Billing & Credits
pxdiff uses a credit-based billing model. You deposit credits upfront, and they’re deducted each time pxdiff captures a screenshot or runs a diff. There are no subscriptions, no per-seat fees, and no surprise invoices.
How credits work
Section titled “How credits work”Every operation that uses compute — capturing a screenshot or diffing two images — costs credits. The cost is based on actual Lambda execution time and memory:
credits = (memoryMb / 1024) × (durationMs / 1000)In practice:
- Captures run on a 2048 MB Lambda. A typical capture taking 5 seconds costs ~10 credits.
- Diffs run on a 512 MB Lambda. A typical diff taking 1 second costs ~0.5 credits.
You’re only charged for what you use. Viewing results, approving snapshots, and managing projects are free.
Free trial
Section titled “Free trial”When you create your first organization, pxdiff grants 50,000 free credits — enough to run thousands of captures and diffs while evaluating the product. Trial credits are granted once per user account, regardless of how many organizations you create.
Deposit tiers
Section titled “Deposit tiers”Buy credits through the billing page in your organization settings:
| Tier | Credits | Price |
|---|---|---|
| Starter | 50,000 | $10 |
| Standard | 150,000 | $25 |
| Bulk | 750,000 | $100 |
Credits never expire. Your balance carries forward until used.
Monthly budget
Section titled “Monthly budget”You can optionally set a monthly budget — a cap on how many credits your organization can consume per calendar month. When the budget is reached, new captures and diffs are blocked until the next month.
This is useful for preventing runaway CI from burning through your balance. Set it in your organization’s billing settings.
Per-organization billing
Section titled “Per-organization billing”Billing is scoped to the organization, not individual users. All projects within an org share a single credit balance. Any org member can trigger captures and diffs; only org owners can purchase credits and manage billing settings.
Usage breakdowns show per-user consumption so you can see who’s using what.
What happens at zero balance
Section titled “What happens at zero balance”When your organization’s credit balance reaches zero:
- New captures and diffs are blocked. The API returns a
402 Payment Requirederror, and CI pipelines will fail at the capture/diff step. - Existing data is safe. Your screenshots, baselines, diffs, and approval history remain accessible. You can still view results and approve snapshots.
- Service resumes instantly once you deposit more credits — no waiting, no support ticket needed.
Balance is checked when a capture or diff is submitted. The actual charge is recorded after the Lambda finishes, based on real execution time. This means your balance may briefly go slightly negative if many operations are in flight simultaneously.
Viewing usage and billing
Section titled “Viewing usage and billing”In the pxdiff dashboard, go to your organization and open the Billing section:
- Balance — your current credit balance and whether your org is within its monthly budget.
- Charges — a paginated history of every charge, showing the operation type (capture or diff), credits consumed, and timestamp.
- Usage — a per-user breakdown of credits consumed in the current billing period (calendar month).