What you get, and how it works
Otium accepts work quickly, buffers it durably, and lets the scheduler wait for the cheapest acceptable compute inside your SLA window. Your client code does not change.
Drop-in OpenAI-compatible API
Point your existing client at our base URL. Batch and job semantics you already know, plus one extension for choosing how long you’re willing to wait.
The deadline sets the price
A wider completion window gives the scheduler more room to wait for a price dip, so it costs less. We launch with the widest tier first, where the difference is largest.
Send a pipeline, not a stage at a time
A seven-stage chain normally pays your whole deadline per step — a seven-day window becomes seven weeks. Send the graph instead and one window covers all of it.
You pick a size, not a model name
Small, medium or large, with a current open model kept behind each. Pooling everyone onto a short list is what makes the batches deep enough to be cheap.
Runs on the compute nobody else wants
Your work waits for cheap capacity instead of reserving expensive capacity — spot and idle GPUs, claimed across regions at the moment the price is right.
Nothing retained, nothing trained on
Inputs and outputs expire on a short TTL after delivery, content never reaches a log, and your data is never used to train or fine-tune anything.
Per-customer encryption
Each customer’s data is encrypted under its own key — unreadable to anyone else, and to a compromised machine. Isolation is cryptographic, not just policy.
A spending cap that stops
Set a monthly ceiling and new work holds at the limit instead of billing straight through it. Prepaid balance, optional auto-refill, no surprise invoice.
Cost per job, measured
Cost per job and cost per million tokens are measured and surfaced directly, so you can see what you paid, on which model, and why.
The lifecycle of a job
Point your client at us
One base-URL change. It’s the OpenAI-compatible batch API you already write against — same client, same request shape, no rewrite and no new SDK.
Tell us when you need it
An hour, a day, a week. That deadline is the price lever: the more slack you can give us, the less the job costs you. If your work is a pipeline rather than a single call, publish it as a workflow and that one deadline covers every stage.
We run it when compute is cheap
Your job sits in durable storage until the scheduler finds cheap capacity, then runs. If a worker is reclaimed mid-job the remaining items re-queue, and you can poll status the whole way.
Results out, inputs expire
You get your output by the deadline. Inputs and outputs expire on a short TTL — we keep token counts and cost, never your content.
Point your client at our base URL.
Otium is in closed alpha. Leave your email and we’ll send an invite when a spot opens — then point your OpenAI-compatible client at our base URL and send your first batch.
No credit card, no spam — one email when your invite is ready.
Closed alpha — onboarding is gated while we calibrate. Already invited? Sign in.