isonim

Describe the app you want to build

Work orderIn pilot


Browse the gallery

The builder is in pilot. Describing an idea here puts it in front of us; it does not start a build.

On the rack

Use them
with or without us.

The framework and the editor are open source. Use them in your own projects.

Apache-2.0

Framework

Yours to use in your own projects, and yours to fork.

/framework
AGPL

Editor

Open for local use. Run it on your own machine.

/editor
Star it on GitHub

PreciselyTwo things, named: the framework under Apache-2.0 and the editor under AGPL, open for local use. The hosting platform is not open source.

At the bench

Three steps.

01

Describe it.

In your own words, in the box at the top of this page.

02

It gets built.

What comes out is plain Nim, on the open‑source framework.

03

It stays running.

Hosted and metered, with hard caps and alerts you set.

The bill

No per-seat tax.

Metered on what the app actually uses, and reconstructible line by line.

Metered on
Requests, CPU-time, egress and storage.Not seats. Adding a teammate does not change the meter.
Caps & alerts
Hard caps and alerts are features, not fine print.You set the ceiling; it is part of the product, not a support request.
Overage
Off by default.A paid plan never charges past its subscription price without you turning it on.
Model tokens
BYOS — your own model subscription does the building.No marked-up tokens on your bill.
The bill itself
Reconstructible.You can see what you used, and why.

Proof & exit

You can leave, and take it with you.

The exit is licensed, published and written down — not a promise you have to take on trust.

Your code

Plain Nim, and yours.

Your app’s code is ordinary source you can read, keep and move.

The framework

Apache-2.0, and forkable.

The thing your app is built on is licensed so that it can outlive us.

The runbook

A published exit runbook.

The steps for leaving are written down, in the open, before you need them.