Skip to main content
Jamf Now or Jamf Pro, India

Jamf Now or Jamf Pro: the question that usually has a third answer.

One product assumes nobody has time to learn it. The other assumes somebody will master it. That is the honest distinction, and it matters far more than any feature grid. But before you pick a side, check your Microsoft bill: a large share of the Indian businesses who ask us this are already paying for Intune inside Microsoft 365 and have never opened the device management blade. We hold a listed Apple Jamf Partner badge and we will still point you at the option we earn nothing from. Remote-first from Gachibowli, Hyderabad.

Choosing between Jamf Now, Jamf Pro and Intune for Apple devices in India
  • Three optionsNot two, and the third is often paid for
  • Under 25 MacsWhere Jamf Now genuinely fits
  • Around 50 plusWhere Jamf Pro starts to earn it
  • Mixed estateUsually points at Intune instead
What actually separates them

Eight factors that decide this, in the order they matter.

Comparing feature tables gets you nowhere, since both platforms enrol Apple hardware and both handle the everyday tasks competently. The decision turns on three softer things: how deep your requirements really go, who is going to sit in the console, and what your device count looks like in two years. Below, in the order that actually changes the recommendation.

Who operates it day to day

Ask this before you count a single device, because it decides more cases than headcount ever does. Now is built for the founder or office administrator squeezing IT between other duties. Pro expects someone who will genuinely learn the platform. Hand Pro to a team with no time for it and you end up worse off than with Now, since a powerful console nobody maintains decays into an unmanaged fleet quicker than a basic one ever would.

How much depth you genuinely need

The basics are well covered at the lower tier: getting devices enrolled, pushing apps, applying restrictions, keeping the OS current, turning on FileVault, locking or wiping something that walks out of the office. The upper tier brings scripts, extension attributes, intricate Smart Group conditions and patch workflows. Do not ask which sounds more impressive. Ask whether you have a requirement in front of you today that the simpler product genuinely cannot express.

Whether you run Windows as well

This is the factor that most often rules out both Jamf tiers, and people raise it last. Windows is simply outside their scope. So a floor holding twenty MacBooks and thirty ThinkPads means running two consoles, writing policy twice, and telling your auditor two separate stories about the same office. Mixed estates usually land on Intune for everything, with Jamf added only where the Mac depth truly justifies paying for a second platform.

Zero-touch deployment, which both support

A device that configures itself the moment an employee opens the box is available at both tiers, provided the hardware was purchased through a channel that can register it to your organisation. We call that out explicitly because buyers keep assuming it is reserved for the expensive tier. It is not. Your procurement route determines whether zero-touch works, not your Jamf licence.

What happens when you grow

There is no cliff edge, no licence wall. What happens is subtler: somewhere in the twenty five to fifty range the hands-on attention each device needs stops fitting into anyone week, and the reports stop answering the questions you are being asked. Upgrading later is a migration rather than a toggle, with devices re-enrolling and policy rebuilt from scratch, so if your hiring plan doubles the Mac count, price that migration into today decision.

What you must prove to auditors and clients

The moment a client security questionnaire, an ISO 27001 assessor or an insurance underwriter asks about encryption coverage and patch levels, a screenshot will not do. You need something exportable, dated and complete. Reporting at the lower tier is serviceable for a handful of Macs; at the upper tier it is genuinely thorough. Firms whose customers audit them almost always outgrow the reporting long before they outgrow the features.

Security beyond device hygiene

Disk encryption, passcode rules, update enforcement, remote lock and wipe are table stakes at both tiers, and the lower one bundles malware and web filtering as well. What neither product is, and this trips people up, is a detection and response platform. Wanting behavioural threat detection on your Macs is a different purchase entirely, and if you already sit inside Microsoft licensing, Defender has probably answered it for you.

Whether you want to run it at all

Everyone forgets the third path: outsource the console entirely. When a business has no interest in learning any management platform, we operate it for them under a 30 minutes response SLA. Notice what that does to the comparison. Most of the case for the simpler product is really a case about protecting your own hours, and if those hours are not yours to spend anyway, the constraint disappears.

Before you choose either

You may already be paying for the answer.

By some distance the most frequent discovery we make in these conversations: the business already owns Intune and had no idea it handles Apple hardware. Fifteen minutes of licence checking can save the entire purchase.

  • Business Premium carries Intune, and so do the E3 and E5 enterprise plans. Plenty of Indian firms bought Business Premium for its security stack and never looked at the device management side of the tenant. Where that is the situation, managing your Macs becomes a configuration project rather than a procurement one.
  • And it is real management, not a token capability. Enrolment, configuration profiles, application delivery, compliance rules and conditional access all function on Mac, iPhone and iPad. The genuine gaps against Jamf are deep macOS customisation and day-one support when Apple ships a new release. Most smaller firms never run into either.
  • Add Windows to the picture and it stops being a close call. A single console, one compliance policy, one conditional access model and no additional vendor contract beats running two platforms, unless your Mac requirements are deep enough to overrule all of that. In an office of fifteen Macs and twenty Windows laptops, they almost never are.
  • Jamf earns its place in specific situations: an Apple-first company, a Mac fleet heading beyond fifty, a design or post-production team with demanding software packaging, or a hard requirement to support a new macOS version on launch day. Those cases are real and we recommend Jamf without hesitation when we see them. They simply do not describe most of the businesses who ask us this question.
Ask us to check what your licensing already covers
How we advise on this

Four things that make our answer worth more than a comparison table.

Feature lists are free and mostly useless. What you are paying for is judgement about which of those features you will never once open, and an adviser willing to point at the option that earns them nothing.

We check your licensing before recommending a purchase

The first thing we look at is what your Microsoft 365 plan already includes, because in a large share of cases Apple device management is already paid for and simply unconfigured. Telling you that costs us a licence sale and earns a client, and it is the single most useful thing we do in these conversations.

We size for the business you will be in two years

The Jamf Now to Jamf Pro move is a migration: devices re-enrol, policies are rebuilt, and it lands at whatever moment you are least able to absorb it. If your hiring plan says the Mac count doubles, we factor that in now. Choosing the simpler tier and paying for a migration eighteen months later is frequently the more expensive path.

We will run it if you would rather not

A lot of this decision is really a question about your own time. If you would rather not own a console at all, we operate the platform as a managed service with a 30 minutes response SLA, which removes the simplicity argument from the decision entirely and often changes the answer.

We know the procurement side, which decides zero-touch

Whether your Macs enrol themselves is determined at purchase, not in the console. Devices need to come through a channel that can register them to your organisation in Apple Business. We advise on this before you order, because it is the one mistake in this area that cannot be corrected afterwards without manual work on every device, forever.

What we would actually recommend

Six real Indian business shapes and the answer for each.

These are the situations we see most often. In three of the six the recommendation is not a Jamf product at all, which is roughly the real-world ratio.

A twelve-person design studio, all Mac

Apple only, no Windows, no dedicated IT person, and design software that needs deploying but nothing exotic. Jamf Now fits well: enrolment, apps, encryption and updates without anybody learning a platform. Watch the growth, because a studio that wins a large client and doubles in a year will feel the ceiling quickly.

A forty-person firm with a mixed estate

Twenty Macs, twenty Windows laptops, the most common shape we see, and the clearest recommendation: Intune, which the firm is almost always already licensed for through Microsoft 365. One console, one compliance policy, conditional access included, no second contract.

An Apple-first business heading past fifty Macs

This is where Jamf Pro earns its place. At this scale the manual attention Jamf Now requires stops being sustainable, the reporting gets thin for compliance purposes, and the deeper configuration starts to have real uses. If the trajectory is clear, going to Pro directly avoids paying for a migration in eighteen months.

A clinic or practice with a handful of iPads

Small device count, high sensitivity, and a strong need to prove encryption and access control rather than configure anything clever. Jamf Now covers this competently, and if the practice already holds Microsoft 365, Intune covers it without an extra contract. The decision usually comes down to whether there are Windows machines in the same room.

A firm whose enterprise clients audit it

SaaS, IT services and consulting businesses get asked for evidence repeatedly, and the ability to export device compliance quickly matters more than configuration depth. Intune usually wins for a mixed estate because compliance connects natively to access; Jamf Pro joins only if the Mac side has requirements Intune cannot meet.

A business with no IT capacity at all

Three Macs, five iPhones, nobody who wants to own a console, and a founder who wants to stop thinking about it. The honest recommendation is often not about the product: pick whichever platform your provider runs well and hand it over. The simplicity difference between the tiers stops mattering the moment the operating burden is not yours.

The two Jamf tiers directly

If it is definitely going to be Jamf, here is where the line falls.

Put Intune to one side and assume Jamf is settled. What separates the two tiers then follows a single consistent shape: the lower one delivers the essentials for almost no operational effort, the upper one delivers everything provided you can staff it.
Feature
Jamf Pro
Jamf Now
Enrolment, apps, restrictions, updates
FileVault encryption and remote lock
Zero-touch deployment
Self-service app catalogue for staff
Scripting and custom automation
Complex Smart Group logic
Basic grouping
Third-party patch management workflows
OS updates only
Granular role-based administration
Limited
Detailed exportable compliance reporting
Basic
Effort to learn and maintain
SignificantMinimal
Right for a founder running IT part time
NoYes
Right for a growing Apple-first business
YesUntil around 25 to 50 devices
All three, side by side

Jamf Now, Jamf Pro and Intune on the points that decide it.

Not a scoreboard, a filter. Nobody wins on row count. Find the three or four rows that describe your actual constraints and let those decide, which for most Indian offices means the Windows question, the operator question and the licensing question.
Jamf NowJamf ProMicrosoft Intune
Manages Windows devicesNoNoYes
Manages Mac, iPhone, iPadYesYesYes
Manages Apple TVYesYesLimited
Zero-touch enrolmentYesYesYes
Deep macOS configuration and scriptingNoThe deepest availableImproving, still behind
Patch management workflowsOS updates onlyFullGood
Complexity to learn and operateLowestHighestModerate
Compliance reporting depthBasicStrongStrong
Conditional access to company dataNoThrough integrationNative
Same-day support for new Apple releasesYesYesUsually delayed
Likely already in your licensingNoNoOften yes
Comfortable device ceilingAround 25 to 50No practical ceilingNo practical ceiling
Second console needed for a mixed estateYesYesNo
How we get to an answer

Five steps, and the first is one short conversation.

This decision does not need a long engagement. It needs somebody to look at four or five facts about your business and tell you the answer plainly.
  1. 1

    Count the estate and check the licensing

    How many Macs, iPhones, iPads and Windows machines, and which Microsoft 365 plan you are on. Those two facts alone resolve the majority of cases, because a mixed estate on Business Premium has an answer that does not involve buying anything.

  2. 2

    Establish who will operate it

    An internal person, a part-time role, or us. This is where the Jamf Now against Jamf Pro question is actually settled, because the tier difference is largely a difference in operating burden rather than in what is technically possible.

  3. 3

    Check the growth and compliance trajectory

    Headcount plans, hiring in design or engineering, and whether enterprise clients are likely to start sending security questionnaires. These determine whether the simple answer today becomes a migration in eighteen months, which is a cost that belongs in the decision now.

  4. 4

    Give a written recommendation with the reasoning

    One page, naming the platform, why, what it will and will not do for you, and what would change the answer. Where the recommendation is that you use something you already pay for, it says so. You should be able to hand that page to somebody else and have it stand up.

  5. 5

    Deploy it, or hand it over, whichever you prefer

    If you want us to implement, we do enrolment, policy, app deployment, encryption and reporting, then either hand over with documentation or continue running it under a managed agreement with a 30 minutes response SLA. If you would rather implement yourself, the recommendation is enough to work from.

The direct questions

What people actually want to know before choosing.

Two things, and the second one is what people underestimate: how deep the product goes, and how much of your week it wants. The lower tier deliberately restricts itself to the essentials so a non-specialist can own it, covering enrolment, apps, restrictions, updates, disk encryption and remote lock or wipe. The upper tier exposes everything macOS permits, scripting and grouping logic and patch workflows and fine-grained admin roles, and it assumes a real administrator is driving. Apple TVs, iPads, iPhones and Macs are all in scope either way. So the useful question is never which product can do more. It is whether anything on your list is beyond the simpler one.

Nobody enforces a ceiling, so this ends up being a judgement call rather than arithmetic. From what we see, the strain appears between twenty five and fifty devices, and it announces itself through reporting rather than a missing button. A client sends a compliance question and you cannot answer it inside an hour. Or you notice how many minutes each individual machine is quietly costing someone. A second trigger is hiring: bring on a design or engineering team and configuration demands climb much faster than the device count alone would predict.

There is a good chance you do not, and if you take one thing from this page, take this. Intune ships inside Business Premium, E3 and E5, and it manages Apple hardware seriously rather than superficially. Sitting on one of those plans with unremarkable Apple requirements means the capability is already bought and waiting. Jamf still wins for Apple-first companies, for deep macOS configuration work, and when you must support a brand new Apple release on the day it lands. Outside those cases, particularly in an office running both platforms, your existing licensing tends to make the decision for you.

They cannot, at either tier, and this single limitation disqualifies Jamf more often than anything else we encounter in Indian offices. Picking Jamf when half your hardware runs Windows commits you to two consoles indefinitely, two policy sets to keep aligned, and compliance answers assembled from two sources every time somebody asks. That overhead never goes away. Pay it when your Mac requirements genuinely demand Jamf depth. Do not pay it merely because the Macs are the newer, shinier machines in the building.

Treat it as a project, not a plan change, and factor that in now rather than discovering it later. Every device re-enrols into the new tenant, configuration and policy get rebuilt instead of migrating across, and your staff notice the disruption. None of this is technically hard, we run these regularly, but it eats calendar time and it never happens at a convenient moment. Where the growth is already visible in your hiring plan, starting on the upper tier usually costs less across three years despite the heavier first-year bill.

Yes at both tiers, which regularly surprises buyers who filed it under premium features. Any Mac or iPhone purchased through a channel capable of registering it to your organisation will bring itself under management the first time it powers on. Procurement decides this, not licensing. A machine picked up from a general retailer needs manual enrolment, and that enrolment evaporates at the next factory reset, so the device silently exits your estate the first time anyone wipes it and stays out until a human notices.

Sufficient for hygiene, yes. Encryption, passcode rules and update enforcement are handled at both tiers, remote lock and wipe work at both, and the lower tier throws in malware and web filtering. Neither, however, is a detection and response platform: no behavioural detections on macOS, no investigation timeline, no alert queue. Deciding you need that is a separate purchase, and organisations already inside Microsoft licensing usually find Defender has covered it. When a purpose-built Mac security product really is justified, Jamf Protect sits naturally alongside Jamf Pro.

The lower tier, yes, without qualification. It was designed for a competent non-specialist to stand up and maintain, and a great many small Indian firms do precisely that with no outside help. The upper tier is a different proposition: a professional instrument that rewards real study. The failure we watch happen goes like this. A business buys Pro for capabilities it genuinely wanted, never carves out the fortnight to learn it, and two years later owns an expensive console holding a configuration nobody has touched since implementation. When the time is not there, either choose the simpler product honestly or hand the capable one to someone who will run it.

Between the two Jamf tiers it is Pro, straightforwardly, since compliance work is mostly the ability to produce evidence when somebody demands it and Pro reporting goes considerably deeper. The more useful answer, though, is that Intune often beats both. Its advantage is structural: compliance state is wired into access, so a device that falls out of policy is denied company data rather than simply appearing on a report as non-compliant. If your team is repeatedly working through enterprise security questionnaires, ISO 27001 findings or DPDP Act reasonable-security questions, that enforcement link is worth more than configuration depth you will never use.

You do, and it costs nothing. Think of Apple Business as the organisational account sitting underneath everything: your device registrations live there, so do Managed Apple Accounts and volume app purchasing, and without it zero-touch enrolment cannot happen at all. Every management platform hooks into it, Intune included. One naming note that causes confusion in vendor conversations: Apple folded the old Apple Business Manager branding into Apple Business during April 2026, so documentation and reseller quotes written before then still say Manager.

Manageable, but permanently second-class, and it is worth understanding why. Because the machine was never registered to your organisation at the point of sale, somebody has to enrol it by hand, and that hand-enrolment does not survive a wipe. Reset the laptop and it walks straight out of your management until a person notices and repeats the exercise. Some existing devices can be pulled into the enrolment programme retrospectively through an authorised reseller, and we check whether yours qualify rather than assuming they do not. For everything you buy from here on, use a channel that can register hardware to your organisation.

Whatever your circumstances actually point to, with the reasoning shown so you can challenge it. Four patterns cover almost every case we see. Windows and Apple mixed together on a Microsoft 365 plan points to Intune. A small Apple-only firm with no IT resource points to the simpler Jamf tier. An Apple-first company beyond roughly fifty devices, or carrying real configuration complexity, points to Jamf Pro. And an organisation with no appetite for operating any console at all points to whichever platform fits, with us running it. Both the licensing and our own work are quoted per engagement, since device mix and operating model swing the numbers too far for a published rate card to be honest. Enquiries get a reply within 4 business hours.
Decide it in twelve questions

Answer these and the platform chooses itself.

This is the sequence we run in the first call. The opening group normally produces the answer on its own. The middle group is the two-year view nobody thinks about until the migration bill arrives. The last group is what an insurer, an assessor or your largest customer will eventually put in writing.

The questions that usually settle it

  • Do you run Windows devices as well as Apple ones?
    If yes, seriously consider Intune before either Jamf tier.
  • Are you licensed for Microsoft 365 Business Premium, E3 or E5?
    Then you already have Intune. Check before you buy anything.
  • How many Macs, iPhones and iPads do you actually have?
    Under 25 favours simplicity. Past 50 favours capability.
  • Who will operate the console, and how much time do they have?
    The most predictive question, and the one least often asked.

The growth questions people skip

  • What will your device count be in two years?
    Moving from Now to Pro later is a migration, not a switch.
  • Are you hiring designers, developers or video staff?
    Those teams create deep configuration needs quickly.
  • Will you need to support a new macOS release on day one?
    A real Jamf advantage, and irrelevant to most businesses.
  • Will device management stay outsourced or come in-house?
    If outsourced, the simplicity argument largely disappears.

What you will be asked to prove

  • Can you export encryption status for every device today?
    The first question on most insurer and client questionnaires.
  • Can you show patch and OS version compliance across the estate?
    Basic in Jamf Now, thorough in Pro and Intune.
  • Can a lost device be located, locked and wiped within the hour?
    All three do this. Test that yours actually works.
  • Is device compliance connected to who can reach company data?
    Native in Intune, and the gap Jamf-only estates most often have.
References

Official documentation

Next step

Tell us your device count and your Microsoft plan.

Those two facts resolve most of this decision in a single conversation. We will give you a written recommendation with the reasoning, including the case where the answer is that you already own what you need and should not buy anything at all. Enquiries answered within 4 business hours.