Pricing and capacity
Start with a plan. Scale with compute.
Monthly workload entitlements, explicit rate limits, and usage-priced acceleration. The effective request limit is the lowest applicable plan, workload, and hardware limit.
Hobbyist
Evaluate the runtime on small CPU workloads.
- 300 SAT solves / month
- 25 Q-State solves / month
- 10 schedules / month
- 10K variables and 100K clauses
- 1-request account ceiling; CPU access
Mini Lab
Build prototypes and small CPU workflows.
- 2,000 SAT solves / month
- 250 Q-State solves / month
- 100 schedules / month
- 100K variables and 1M clauses
- 3-request account ceiling; CPU access
Launch Pad
Expanded API access with Pro and L4 eligibility.
- 6,000 SAT solves / month
- 750 Q-State solves / month
- 300 schedules / month
- 1M variables and 8M clauses
- 10-request account ceiling; CPU + L4
Lotus Fleet
Higher shared capacity across every compute class.
- 14,000 SAT solves / month
- 1,750 Q-State solves / month
- 700 schedules / month
- 2M variables and 12M clauses
- 25-request account ceiling; CPU + L4 + H100
Compute settlement
Plan access first. Hardware usage second.
CPU entitlement is included in each plan. Overage and GPU execution draw from API credits.
$0$0.01 + $0.02/min$0.05 + $0.02/min$0.05 + $0.02/min$0.30 + $0.20/minDedicated capacity
More model size. More throughput. Your hardware.
Dedicated deployments are optimized for maximum model size and throughput. Limits are based on the hardware provisioned for your account rather than shared-cloud ceilings.
Private runtime
A premium deployment, not another shared tier.
- Dedicated infrastructure with no multi-tenancy
- Private API endpoint and private workload boundary
- Usage on the provisioned machine without shared-plan solve quotas
- No shared-cloud rate limits or concurrency throttling
- Custom solver configuration and deployment support
- Air-gapped operation available
Anytime runtime
A deadline returns a decision, not an empty wait.
Partial results include residual violations and provenance. Shared capacity has a 30-minute timeout; dedicated longer-running capacity is available by arrangement.
Developer access via GitHub Sponsors
Purchase Navokoj API compute credits through GitHub Sponsors. Sponsor ShunyaBar Labs to receive credits at 1.5x your sponsorship amount.
- Purchase credits via GitHub Sponsors.
- Email contact@shunyabar.foo with the transaction ID and your Navokoj account email.
- We provision or credit the account associated with that email.
Billing: compute time is measured per second. The API response and ledger are authoritative.
Canonical API contract
Plans, workloads, and hardware each set a limit.
The effective request limit is the lowest applicable value. This prevents a high-volume CPU entitlement from overrunning a reserved GPU queue.
Account plans
| Plan | Monthly | SAT / mo | Q-State / mo | Schedules / mo | Vars / clauses | Concurrent | Hourly | 30 sec |
|---|---|---|---|---|---|---|---|---|
| Hobbyist | $0 | 300 | 25 | 10 | 10K / 100K | 1 | 120 | 5 |
| Mini Lab | $2 | 2,000 | 250 | 100 | 100K / 1M | 3 | 1,000 | 15 |
| Launch Pad | $5 | 6,000 | 750 | 300 | 1M / 8M | 10 | 10,000 | 40 |
| Lotus Fleet | $10 | 14,000 | 1,750 | 700 | 2M / 12M | 25 | 50,000 | 80 |
Per-offering requests every 30 seconds
| Offering | Hobbyist | Mini Lab | Launch Pad | Lotus Fleet |
|---|---|---|---|---|
| Nano | 5 | 15 | 40 | 80 |
| Mini | 2 | 6 | 16 | 32 |
| SUTRA (`engine: nitro`) | 3 | 10 | 30 | 60 |
| Pro | - | - | 4 | 10 |
| Ensemble | - | - | - | 2 |
| Q-State | 2 | 4 | 8 | 16 |
| Scheduling | 1 | 2 | 4 | 8 |
| Diagnostics | 5 | 10 | 20 | 40 |
| Batch requests | 1 | 2 | 4 | 8 |
Hardware admission and queue ceilings
| Constraint metric | Standard CPU | L4 GPU | H100 GPU |
|---|---|---|---|
| 30-second request ceiling | 60 | 6 | 3 |
| Concurrent request ceiling | 8 | 3 | 2 |
| Boolean variables | 1,000,000 | 100,000 | 2,000,000 |
| Boolean clauses | 8,000,000 | 300,000 | 12,000,000 |
| XOR variables / constraints | 1,000 / 500 | 10,000 / 5,000 | 100,000 / 50,000 |
| Q-State nodes / states | 1,000 / 16 | 15,000 / 20 | 100,000 / 50 |
| Scheduling resources | 100 | 200 | 1,000 |
Account concurrency spans hardware pools; each pool also enforces its own ceiling. A batch consumes one
batch-request unit and one solver, account, hardware, and hourly unit per submitted model. GPU access is
plan-gated and usage-billed. GET /v1/pricing is the machine-readable source of truth for policy version, quotas, bursts, and prices.