mojojojo
One mojojojo credit is $0.001 and buys milliseconds here.
| What | Rate | Works out as | 1000 credits ($1) buys |
|---|---|---|---|
| Browser mojojojo.js, WebAssembly |
free, unlimited | runs on the caller's machine | everything |
| CPU one core, 2 GB |
1 credit / 10000 ms | $0.36 / core-hour | 2.8 core-hours |
| GPU RTX 5090, time-sliced |
1 credit / 2000 ms | $1.80 / GPU-hour | 33 GPU-minutes |
Reserve a continuously running Python or Mojo process for WebSockets, warm models, custom servers, and in-memory indexes. Reserved capacity is billed while idle; normal scale-to-zero functions remain the economical default for bursty traffic.
| Profile | Reserved resources | Rate | Approx. 30 days if never stopped |
|---|---|---|---|
| CPU nano | 0.25 shared CPU · 512 MiB | 200 credits · $0.20/hour | $144 |
| CPU 1 | 1 CPU · 2 GiB | 750 credits · $0.75/hour | $540 |
| CPU 2 | 2 CPU · 4 GiB | 1,400 credits · $1.40/hour | $1,008 |
| GPU 24 | 4 CPU · 16 GiB · 24 GiB GPU | 3,500 credits · $3.50/hour | $2,520 |
Charged hourly in advance and cancelled at the next renewal. Failed builds are free. Billing pauses if reserved capacity is unavailable. Execution inside the reserved profile is included; storage above the included allowance remains separately metered.
Durable vector projects with exact and performance search behind one API.
per 1,000 queries
Predictable exact retrieval with no idle fee.
per 1,000 queries
Accelerated search for larger collections.
250,000 documents per project
Batch upserts, metadata, durable documents, and API access included.
Shared usage is metered against the same credits as compute. Reserved capacity can be managed from the Vector dashboard.
Tenant-isolated Postgres JSONB namespaces with API-key and session access.
Up to 64 KiB per JSON value and 100 MiB total per database on the shared tier.
Search text uses normal vector upsert/query rates; storing and reading JSON has no execution charge.
The shared data preview has no idle-instance fee. Dedicated Postgres will be a separate tier when workloads need SQL connections, extensions, or stronger isolation.
Per account, for deployed sites, models, and user-uploaded assets.
Only storage above the included gigabyte. Usage is visible in Cloud.
Public assets are served from mojojojo's global static domain with no delivery surcharge.
The clock starts when your program starts. Interpreter startup, the sandbox, and the process fork are ours. Warm slots make it about 60ms end to end anyway.
Your imports are read out of your code and installed by uv into a cached environment. First time for a package set: a second or two. Billed: nothing.
Transpiling your kernels to Mojo and compiling them happens on our machines, on our clock, after your run has returned.
Every new mojojojo account gets 1000 credits — $1 of compute the first time it runs something here. No card, no trial clock. At the CPU rate that is nearly three core-hours, which is a lot of backtests.
One grant per account, ever. Server-side runs need an account for exactly this reason: free compute behind an anonymous endpoint is free compute per request, and it would be strip-mined within a day. The browser runtime needs no account because it costs us nothing.
| Job | Time | Cost |
|---|---|---|
| A 40ms data transform, called 1000 times | 40 s | 4 credits — $0.004 |
| A backtest that takes 3 s (native, after the first run) | 3 s | 0.3 credits — $0.0003 |
| An hour of continuous CPU work | 60 min | 360 credits — $0.36 |
| Ten minutes of GPU | 10 min | 300 credits — $0.30 |
Sub-credit runs are not rounded up. Milliseconds accrue against your balance and a credit moves when they cross the rate, so a thousand 40ms calls cost the same as one 40-second call.
Capacity expands as paid demand grows. The prices above do not change, and queue time is never billed.