
Jamf built a system to cap daily AI spending per engineer.
It restricts premium models at 80% and 100% of budget.
A low-cost model stays available, so work continues.
What happened
Jamf, which manages Apple devices for over 76,000 organizations, built a system using AWS services to enforce daily per-user spending limits on Amazon Bedrock. The system denies access to the Anthropic Claude Opus model at 80% of the daily budget and Claude Sonnet at 100%, while keeping the low-cost Claude Haiku available.
Why it matters
The system gives Jamf per-user cost visibility and accountability for AI usage, which is hard because AI spend scales with behavior rather than provisioned capacity. The company found that cost governance actually accelerated adoption, as leadership became comfortable expanding AI access once spending was observable.
What to watch
The operational cost of the enforcement system is under $10/month for hundreds of engineers, but Amazon Athena query costs must be managed by keeping the log schema lean and using a pre-aggregated cost view. The system runs every 15 minutes and restrictions take effect without requiring re-authentication.
Ask the AI about this article →
The challenge Jamf addressed is that AI costs scale with user behavior, not with provisioned infrastructure, making them invisible until the bill arrives. This makes proving ROI difficult, which can slow down broader AI adoption within a company. By building a system to measure, restrict, and notify on per-user spend, Jamf created the accountability needed to confidently expand access.
The solution uses a serverless architecture on AWS: an Athena view turns token counts into dollar amounts, a Lambda function runs every 15 minutes to compare spending against budgets, and Customer Managed Policies enforce the restrictions. A notable design choice is the system's idempotency, meaning each run recomputes the full restriction list from the day's cumulative spend, which simplifies the logic and requires no rollback procedures.
A key insight from running the system is that governance drove adoption, not restriction. The hard per-user cap gave leadership the confidence to increase the number of AI-enabled engineers. The article recommends keeping a low-cost model always available and treating the pricing map as a critical artifact that must be updated when new models are enabled.
For example, today's edition would include:
AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.
Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. Q&As are published on this page for other readers too.
Anthropic PBC debuted Claude Fable 5.1 and Claude Mythos 5.1, its most capable large language models to date
South Korea's copper clad laminate (CCL) exports surged 42% in the reported period, driven by strong demand fr…

Marvell's CTO stated that power and density bottlenecks are driving adoption of co-packaged optics (CPO) in AI…

Anthropic launched Claude Fable 5.1 and Mythos 5.1, its most capable AI models yet, with gains in agentic codi…

Anthropic is launching its watermark verification API, letting approved organizations check whether text conta…

OpenAI said its next model, Astra, will release soon, but only a small group of "alpha testers"—including the…
