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.

$0
forever
  • 300 SAT solves / month
  • 25 Q-State solves / month
  • 10 schedules / month
  • 10K variables and 100K clauses
  • 1-request account ceiling; CPU access
Get API access

Mini Lab

Build prototypes and small CPU workflows.

$2
per month
$20 annually - two months included
  • 2,000 SAT solves / month
  • 250 Q-State solves / month
  • 100 schedules / month
  • 100K variables and 1M clauses
  • 3-request account ceiling; CPU access
Get API access

Lotus Fleet

Higher shared capacity across every compute class.

$10
per month
$100 annually - two months included
  • 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
Get API access

Compute settlement

Plan access first. Hardware usage second.

CPU entitlement is included in each plan. Overage and GPU execution draw from API credits.

Included CPU Within monthly entitlement $0
CPU overage Up to 1M billable clauses $0.01 + $0.02/min
Large CPU Above 1M billable clauses $0.05 + $0.02/min
L4 GPU Usage billed $0.05 + $0.02/min
H100 GPU Usage billed $0.30 + $0.20/min

Dedicated 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.

Dedicated deployments from $500/month. L4: from $500/month RTX 5090: from approximately $925/month Indicative 24/7 pricing: current GPU infrastructure reference cost plus $200/month. Final pricing depends on region, availability, and hardware. Talk to us about capacity

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.

  1. Purchase credits via GitHub Sponsors.
  2. Email contact@shunyabar.foo with the transaction ID and your Navokoj account email.
  3. 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

PlanMonthlySAT / moQ-State / moSchedules / moVars / clausesConcurrentHourly30 sec
Hobbyist$0300251010K / 100K11205
Mini Lab$22,000250100100K / 1M31,00015
Launch Pad$56,0007503001M / 8M1010,00040
Lotus Fleet$1014,0001,7507002M / 12M2550,00080

Per-offering requests every 30 seconds

OfferingHobbyistMini LabLaunch PadLotus Fleet
Nano5154080
Mini261632
SUTRA (`engine: nitro`)3103060
Pro--410
Ensemble---2
Q-State24816
Scheduling1248
Diagnostics5102040
Batch requests1248

Hardware admission and queue ceilings

Constraint metricStandard CPUL4 GPUH100 GPU
30-second request ceiling6063
Concurrent request ceiling832
Boolean variables1,000,000100,0002,000,000
Boolean clauses8,000,000300,00012,000,000
XOR variables / constraints1,000 / 50010,000 / 5,000100,000 / 50,000
Q-State nodes / states1,000 / 1615,000 / 20100,000 / 50
Scheduling resources1002001,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.