Pricing
Simplr has two billing models that work side by side:
- Credit-based — for API checks (identity, email, phone, device, RUM, edge, order fraud) and AI features like AI Release Notes. You pick a plan with monthly included credits and pay for what you use.
- Per-device — for Device Management (MDM). You pay per enrolled device, per month, on top of a Starter or higher plan.
Plans & credits
Every account has a subscription plan. Each plan includes a monthly credit allowance; API calls consume credits based on the check type. Run out and you can top up with credit packs or move to a higher plan.
| Plan | Monthly | Annual | Included credits / month | Maximum available credits | API keys / webhooks | RUM retention | Support |
|---|---|---|---|---|---|---|---|
| Free | $0 | $0 | 1,000 | 1,000 | 1 / 1 | 7 days | Community |
| Starter | $49 | $490 | 5,000 | 25,000 | 3 / 3 | 14 days | |
| Growth | $199 | $1,990 | 25,000 | 100,000 | 10 / 10 | 30 days | Priority |
| Enterprise | $999 | $9,990 | 100,000 | Unlimited | Unlimited | 90 days | Dedicated |
Annual billing includes two months free (about 16.7% compared with twelve monthly payments). Included plan credits reset each billing cycle; purchased top-up credits remain in the account balance. The maximum-available limit includes unused monthly allowance, the purchased balance, and a pending pack purchase.
| Capability group | Available from |
|---|---|
| Risk checks, RUM, edge logs, order fraud, feature flags, feedback, releases, notifications, journeys, network logs, AI gateway | Free |
| Webhooks, analytics, operations, automation, support email, supported third-party integrations, MDM | Starter |
| GitHub automation and AI code review, self-healing, incident investigation, automated test verification, SLA policies, agent learning, AI roles, marketing | Growth |
Enterprise includes every capability with higher limits, retention, credits, and dedicated support. The dashboard plan selector reads this catalogue from the billing API so availability stays aligned with enforcement.
What credits pay for
Credits are shared across production features. Use the allowance on your plan for any mix of the following:
| Feature | Credit cost | Included work |
|---|---|---|
| Basic email risk | 1 per check | Disposable email, patterns, velocity, and ML scoring |
| Standard email risk | 2 per check | Basic checks plus domain intelligence |
| Premium email risk | 12 per check | Standard checks plus breach and deliverability checks |
| Phone and SIM-swap check | 1 per check | Carrier, porting, and phone-risk signals |
| Order fraud | 1 per order | Profiles and cashier actions are free |
| RUM session | 1 per session | Errors and Web Vitals included |
| RUM network capture | +1 per session | 2 credits total |
| RUM session replay | +3 per session | 4 credits without network capture; 5 credits with it |
| Edge logs | 0.3–1 per 1,000 logs | The rate falls automatically with monthly volume |
| Feedback AI enrichment | 2 per item | Transcription, summary, classification, and priority |
| PR impact analysis | 3 per merged PR | Repository-aware change analysis |
| AI release notes | 5 + 1 per 25 changes | Capture and publishing remain free |
| Feature flag overage | 6 per 1,000 config requests | The first 1,000,000 requests each month are free |
| Automation run | 2 per run | Rules, runbooks, approvals, and audit history are included |
| Automated test verification | 2 per run | Test evidence is attached to the linked work item |
| Incident investigation | 5 per investigation | Connected AI, MongoDB, and Cloud Logging context |
| Marketing campaign concepts | 5 per campaign | Three channel-aware campaign concepts |
| Marketing image | 10 per image | Generated image and stored asset |
| Marketing video | 50 per video | Generated video and stored asset |
| Marketing optimization | 3 per variant | Evidence-led creative variant |
Usage through test API keys is recorded but consumes zero credits. RUM sessions shorter than one second are treated as bounce sessions and refunded. Dashboard views, the unified inbox, API journeys, release capture, rules and runbooks, SLA policies, notifications, supported integrations, and team seats do not consume credits on their own when available on your plan.
Top-up packs range from $5 for 1,000 credits to $1,000 for 500,000 credits, reducing the unit price from $0.005 to $0.002 per credit.
| Pack | Price | Price per credit |
|---|---|---|
| 1,000 credits | $5 | $0.005 |
| 5,000 credits | $20 | $0.004 |
| 25,000 credits | $75 | $0.003 |
| 100,000 credits | $250 | $0.0025 |
| 500,000 credits | $1,000 | $0.002 |
Device Management (MDM)
MDM is billed per enrolled device, per month — a separate meter from check credits. It is available on Starter and higher plans.
| Price | $2 per enrolled device / month |
| What counts | Any enrolled device whose state is not deleted — deleted or fully unenrolled devices are not billed |
| Included | Unlimited policies, groups & bulk commands, both enrollment modes (fully managed & work profile), continuous compliance with grace periods, and an append-only audit trail with CSV exports |
| Plan requirement | Starter, Growth, or Enterprise |
How metering works
- Each enrolled device is counted once per billing cycle, regardless of how many policies or commands you apply to it.
- Device counts are reconciled daily and reported to Stripe as the quantity on a per-device subscription item — so your invoice always reflects the fleet you actually manage.
- Unenroll a device and it stops billing the next cycle. There's no charge for devices you've removed.
- Both fully-managed and work-profile devices are billed at the same per-device rate. The MDM meter is monthly; the subscription plan can be monthly or annual independently.
Example
Managing 120 devices on the Growth plan:
Growth plan ............................ $199 / mo
120 devices × $2 ....................... $240 / mo
---------
Total .................................. $439 / mo
For the full walkthrough, see the MDM guide.
Feature Flags
Feature Flags use the same shared credits as the rest of Simplr. A request is counted every time an SDK fetches the flag configuration for a live environment.
| Free tier | 1,000,000 requests per month, free |
| Price | 6 credits per 1,000 requests above the free tier (nominally $0.03 at $0.005 per credit) |
| What counts | One request per SDK config fetch (on initialize() and each refresh()). Local isEnabled() evaluations are not billed — they never hit the network |
| Included | Unlimited flags, percentage rollouts, user targeting, rules, production & sandbox environments, audit log, rollback, and test-gated progressive rollout |
| High volume | Custom pricing for very high request volumes — talk to sales |
How metering works
- The SDK fetches the full flag config once on init and again on each scheduled refresh — not on every
isEnabled()check. Evaluation is local and deterministic, so the vast majority of flag checks cost nothing. - Tune your refresh interval to trade freshness against request volume. A 60-second refresh is ~43,200 requests per SDK instance per month; a 5-minute refresh is ~8,640.
- The free 1,000,000 requests reset at the start of each billing cycle. Test-key requests consume no allowance or credits. Usage and estimated cost are shown live on the Billing page in the dashboard.
How that compares
| Provider | Model | Indicative cost |
|---|---|---|
| PostHog | Per-request after free tier | 1M free, then $0.10 / 1k at the first paid tier |
| LaunchDarkly | Service connections + client-side MAU | Limited free tier; paid client-side MAU from $10 / 1k |
| Simplr | Shared credits | 1M free, then 6 credits / 1k |
Example
An app whose SDK refreshes flags every 5 minutes across 3 instances:
3 instances × ~8,640 requests ......... ~25,920 requests / mo
Free tier ............................. 1,000,000 requests / mo
----------------------
Billable .............................. 0 → $0.00 / mo
For the full walkthrough, see the Feature Flags guide.
AI Release Notes
AI Release Notes are billed in credits — the same credits your plan includes — so the AI never runs for free. Capturing changes, mapping them to environments, flag linkage, publishing, and the public page are all free; you only spend credits when the AI writes.
| AI release note generation | 5 credits + 1 credit per 25 changes summarized |
| AI impact analysis (per merged PR) | 3 credits — reads the changed code against the rest of the repo and comments on the PR |
| Free | GitHub App connect, CLI/CI ingest, environment mapping, feature-flag linkage, publishing & the public /r/<slug> page |
| Credit price | Drawn from your plan's monthly allowance, or top-up packs from $0.005 down to $0.002 per credit |
How metering works
- A release note costs
5 + ⌊changes / 25⌋credits — a typical note over a handful of merges is 5 credits (≈ $0.01–$0.025 using top-up credit rates). - The impact analysis runs only on merge (not on every push), and is charged 3 credits per merged PR. If your balance can't cover it, the AI step is skipped and the PR comment says so — you're never silently charged or silently given it for free.
- All AI spend is recorded on the Billing page as
usage_deductiontransactions taggedrelease_notes/code_analysis.
Example
A team merging ~40 PRs/month and cutting 8 releases:
8 release notes × 5 credits ........... 40 credits
40 merge impact analyses × 3 ......... 120 credits
-----------
Total .................................. 160 credits (≈ $0.32–$0.80)
For the full walkthrough, see the AI Release Notes guide.