Free Bandicot core
Available nowSolo is free with every capability for one profile. Bring a provider key, a local model, or both; a provider's own bill stays yours.
Paid plans add profiles to an account. Bandicot does not resell model tokens.
For model comparisons on real work
Run the same project on different models and Bandicot keeps the tokens, cost and changes of each. Compare runs on evidence, not memory.
Solo is free for one profile · providers bill you directly
The problem
Model comparisons live in notebooks and screenshots, and nobody remembers which prompt or cache state produced which number.
The promise
The ledger records each turn per model. Versions record each output. You compare like with like.
The picture
The plan
Every card names its status. Available now means you can use it today; in development and direction mean it is not shipped yet.
Solo is free with every capability for one profile. Bring a provider key, a local model, or both; a provider's own bill stays yours.
Paid plans add profiles to an account. Bandicot does not resell model tokens.
Bandicot gives every agent a project, tools, a session that survives restarts, approvals, and a clear place to stop.
The native host owns execution facts. The model proposes work; it does not certify a write, spend, or success.
Keep files, context, plans, and decisions with the project instead of losing them in a disposable chat.
A session is anchored to a project boundary so a pivot starts from an intentional context, not accidental history.
Close a client or reconnect after a pause without turning the work into a brand-new conversation.
The host records session state and clients reattach to it. A browser view does not become the source of truth.
When work can change files or systems, Bandicot makes the decision visible before the effect lands.
The approval boundary fails closed when an action is not allowed. The model cannot grant itself permission.
Use a local endpoint, a private runtime, or a remote provider without rebuilding the project around one model lab.
Provider adapters keep model choice separate from project state. Remote providers receive the prompts sent to them.
See the tokens, cache reads and cost of every turn, per session, profile and model, and the habits behind them.
Bandicot reports what the provider or local runtime exposes. A provider that hides usage shows a dash, never a guess.
Keep a legible trail of the turn and its effects so a pivot can be reviewed instead of guessed at.
The host treats state changes as recorded events. Reverting is itself part of the history.
Pick a small local model from a pinned catalog and install it in one click, checksum verified.
Eight chat models from about 1.25 to 4 GB of memory, on Apple Silicon. Small models suit private, light work; they are not frontier models.
Before a local model downloads, Bandicot checks it against your Mac's GPU memory budget and free disk.
The fit check reads the Metal working-set budget, not physical RAM, and counts weights, context cache and a stated reserve.
For you if
People who compare models on real tasks.
Not for you if
Pure inference serving at scale.
The offer
Team · $8.99 a month · up to 3 profiles
No contract. Cancel any time from your account and keep the plan until the end of the period you paid for.
Solo is free for one profile · providers bill you directly
Left off this page
Bandicot does these too, but they are not why this page exists. Anything marked in development or direction is not shipped yet.
Questions
No. It records what each run did and spent so your comparison has a trail.
Yes, from a pinned catalog of small models checked against your Mac's GPU memory, or any compatible endpoint you connect.
Yes. Cache reads and fresh tokens are recorded separately.
Experiment Ledger
Solo is free for one profile · providers bill you directly
Explore another angle
Solo is free for one profile · providers bill you directly
Start free