Simple pricing for professional work
Start free. Upgrade when your volume does.
Credit rates (per observation file unless stated)
All plans include secure data transmission (TLS 1.3) · GDPR compliant · No hidden fees
No subscription? No problem.
- No subscription required
- All quality analysis modes
- Per-file limit follows your plan (500 MB on Pay-per-use)
- Full quality analysis report
- Valid for 365 days
- No subscription required
- All quality analysis modes
- Per-file limit follows your plan (500 MB on Pay-per-use)
- Full quality analysis report
- Valid for 365 days
- Best value
- All quality analysis modes
- Per-file limit follows your plan (500 MB on Pay-per-use)
- Full quality analysis report
- Valid for 365 days
Everything you need, nothing you don't
| Feature | Free | Pro | Business |
|---|---|---|---|
| Credits / month | 25 | 500 | 2500 |
| Max file size | 100 MB | 500 MB | 1 GB |
| Storage | 500 MB | 5 GB | 20 GB |
| Team seats | 1 | 1 | 5 |
| Crux quality check | |||
| Flux format conversion | |||
| Apex high-precision engine | |||
| Axis coordinate transform | |||
| Batch job processing | |||
| API access (keys) | |||
| Pay-per-use credits | |||
| CSV & Excel export | |||
| Email support (2 business days) | |||
| Priority email support (1 business day) |
SSO, on-premise deployment, or more than 2,500 credits a month. Custom terms and invoicing. Talk to Sales
75 one-time onboarding credits
New accounts receive enough trial credits for one PPK run plus one PPP file, in addition to the Free monthly allowance. Trial credits normally expire after 14 days; check the expiry shown in your account. Eligibility and processing prerequisites still apply.
Refund boundaries
| What happened | Credit outcome |
|---|---|
| Credit-hold positioning runs: reported platform, engine or output-validation failure. | The held credits are released when the failure is settled, including reported engine failures after compute starts. |
| Legacy charged runs: recognized infrastructure failure such as dispatch, missing stored file, ephemeris download, engine startup, internal error, or unusable analysis output. | Automatically credited back in full. |
| Legacy charged runs: the positioning engine explicitly rejects the input before its first compute binary starts. | Automatically credited back in full. |
| Legacy charged runs: compute started but the data could not be solved, or the failure is not on the refundable-code list. | Charged. Running the engine consumes compute even without a usable result. |
| Credit-hold positioning runs: user cancellation before or after the recorded engine-start marker. | Before the marker: release the hold. After the marker: charge it. The marker is set before executor entry, so waiting for an engine slot can already count as started. |
Legacy automatic credit reconciliation runs every 10 minutes for tasks submitted within the current UTC calendar month. A legacy task that fails after its submission month ends is outside that refund window. Credit-hold positioning runs use their own settlement path instead. The month window applies to the monthly allowance. A purchased credit is returned to your purchased balance whenever the run fails for a reason we refund, with no window.
This table describes quality-check and precise-positioning task credits, not subscription or cash refunds. A failure count is not a refund receipt; consult your credit ledger for the settled amount. Other or unclassified failures are not proof that your data was at fault.
Here's how often we fail.
Live reliability readings load when you open this page.
Success rate = completed ÷ (completed + failed). Only retained tasks submitted in the last 30 days are counted; queued and running tasks are excluded. Restarts replace earlier attempts, and deleted tasks are absent. Median time covers completed tasks with valid start/end times, excluding queue time. Readings are cached for five minutes; reload for a newer snapshot. Flux counts conversion jobs; a batch is completed when at least one file succeeds. Flux failures are unclassified. Axis counts successful and failed coordinate-transform requests started in the last 30 days, once per request including batches, from the tracking start shown below. Earlier success-only history is excluded. Axis HTTP 4xx responses are input rejections; HTTP 5xx and unreachable services are system failures. Flux runtime is not recorded.
Common questions
Can I change my plan at any time?
Yes. You can upgrade or downgrade any time from your account settings. Upgrades take effect immediately; downgrades apply at the end of your billing period.
What happens when I use up my monthly credits?
Once your plan's monthly credits are used up, you can purchase Pay-Per-Use credits to keep processing, with no need to wait for the next cycle.
Is there a free trial for Pro or Business?
The Free plan is our trial: all four products at small scale, no credit card required. Upgrade when your volume grows; downgrading later is self-serve.
Do you offer discounts for research institutions or NGOs?
The Free plan is designed for coursework-scale academic use. For labs or organisations with higher volume, contact us at support@posflow.ai and we will find a fit.
What payment methods do you accept?
Checkout runs through PayPal, which also accepts major credit and debit cards without a PayPal account.
How does Pay-Per-Use work?
Credits can be purchased in bundles and are consumed per billable file, at the rate of the product and mode you run. Credits are valid for 365 days from purchase.