Five surfaces, one account.
The same models, the same wallet and the same local billing behind everything — so you pick the surface that fits the job instead of a subscription that fits a vendor.
- CLI (works over SSH)
- VS Code extension
- Web chat
Koda Assist
The coding assistant. It plans, edits, runs and verifies your change in an isolated sandbox before handing it back — in your editor or your terminal.
- VS Code extension and a `koda` CLI that works over SSH
- Retrieval scoped to your own repository
- Every iteration metered and shown, not estimated
# index the repo once, then work against it $ koda repo index . $ koda run "harden the refund endpoint" plan → retrieve → edit → run → verify ✓ tests pass in an isolated sandbox ✓ diff shown before anything is written
Koda Chat
Conversations organised into projects, with files and images attached. It can search the web and write documents back out when a question needs more than a reply.
- Projects and shared conversations for a team
- Attachments and image understanding
- Web search and document generation, where configured
project "Q3 payments migration" ├─ conversation · shared with the team ├─ attachment · provider-spec.pdf ├─ image · a screenshot of the failure └─ output · a document you can download
Koda Build
Describe the app your business needs in plain language and Koda writes it, then publish it. Payments are built in, not a later integration — the checkout works on the rails your customers already have.
- Storefronts, bookings, invoicing, inventory, school fees, tickets
- Publishes to a live URL you can send to a customer
- Collects on mobile money, USSD, transfer and card
// describe it the way you'd explain it to a person "a booking page for my salon, deposit on mobile money, SMS the customer a slot" ✓ template · booking ✓ checkout · mobile money · USSD · transfer ✓ published · a live URL you can send
Koda Design
Generate and edit the visual assets an app or a campaign needs, on a canvas you can keep working in, then publish them straight into what you built.
- Generate, refine and version assets in place
- Publishes to the same account and storage
- Feeds directly into what Koda Build generates
canvas ├─ generate // from a prompt or a reference ├─ refine // keep editing, don't restart ├─ version // every save is recoverable └─ publish → straight into your Build app
Koda Review
A reviewer that knows African payment infrastructure. It flags the mistakes that pass code review everywhere else and only break on a real handset — money in the wrong unit, an unsigned webhook, a callback that cannot be retried safely.
- Minor-unit and currency-handling errors
- USSD session and webhook-signature checks
- Idempotency gaps that allow a double credit
✗ amount stored as a decimal naira value → use integer minor units (kobo) ✗ webhook handler trusts the request body → verify the signature before crediting ✗ credit applied per callback, not per reference → a provider retry will credit twice
The parts that make the price possible.
Affordability here is an engineering result, not a discount. Four decisions do most of the work, and they apply the same way whichever surface you're using.
Open models by default
Routine work runs on fast, inexpensive open models. A frontier model is used when the task calls for it — and you're told which lane ran.
Prepaid local billing
Top up on the rails you already use. Money is handled in integer minor units end to end, and a retried payment can't credit twice.
Metered per run
Each run writes a ledger entry. Your balance moves while you watch it, so there is never a bill to reconstruct after the fact.
Your code stays yours
We don't train on your code. Teams get isolated data; regulated customers can be partitioned into their own schema or pinned to a region.
Try it on something real.
Free to start — top up a prepaid balance when you need more than the free lane.