Start

A development computer, not a server.

Bettik is a machine of your own that keeps running while you are away, with Claude on it. You talk to it — from a laptop, from the Claude app on your phone, by voice — and it installs, clones and runs the environments your work needs.

There are four things to know the names of. Everything else in these pages is one of them, seen closer.

box

Your machine. One per person to start with, always on, named home.<handle>. Nobody shares it.

workbench

Where you work on the box: one container with a shell, git, node, psql and Claude Code in it, and every environment mounted under ~/environments. Reached from the Claude app, or by ssh.

environment

A thing that runs: a runtime, the services beside it — a database, say — and a directory, at its own address. A game, an app, a kit, a starter: whatever its author made it. Cheap to install, cheaper to clone. You can have many.

template

An environment template: a frozen copy of an environment. Save an environment and its whole directory, data included, becomes the next saved environment of one of your templates, to install again on any box; publish a version of it to share by link.

The tooling lives in the workbench, once; the runtimes live in environments, one each. That split is what makes an environment small enough to clone in seconds with its database, and what lets one editor see every project at once.

How you drive it

Not with a dashboard, mostly. Bettik is an MCP server: a set of things Claude can do on your box — install an environment, clone it, save it, read its logs. You add one connector once, and then every Claude you have — the app, Claude Code, a session running on the box itself — can do them. The pages here describe the tools as things you say, and what happens on the box when you say them.

The quick start takes about ten minutes and ends with an environment of yours at its own address and Claude on your box. The three ways to work are what it is actually for.

What it is not

It is not a laptop replacement — it is a decoupling. Your compute stops being the thing you carry: it works while you sleep, a build never pins the machine you type on, you can have several and fork them, and nothing is lost when the client dies. A dropped phone is a dropped phone; the work never left the box.

It is also not a server for other people. An environment's address opens for you and nobody else. When something you built is ready for the world, that is a deploy somewhere else; Bettik is where it was made.