CLANKER.NET

Deploy Your Own Clanking Machine

The replicator behind your software factory. Orchestrate and coordinate agent development environments on infrastructure you control.

Open the app See how it works

What it makes

Working environments, made to order.

A host in your accounts

One machine that runs everything: a server you already have, or a new one in the cloud you choose.

A workspace per engineer

Own hostname, own database if needed, the project already running, agent tooling inside.

A coordination server

Where engineers and their agents hand off work.

How it works

Three steps.

  1. 01

    Describe your project

    A standard dev-container file in your repository says what a workspace is.

    .devcontainer/devcontainer.json
  2. 02

    List it in your fleet

    One fleet file per machine names its repositories. Run the workflow: your own CI stands the machine up in your accounts.

    clanker.yml · host-up · provision
  3. 03

    Your team works in it

    Every engineer gets a workspace with your project running, on your domain over your private network, plus the coordination server.

    ssh [email protected]

Environments

Staging and production, the same way.

One file per repository

Sites, storage and names are described beside the code, one stage at a time.

Reviewed before it changes

Every change shows its plan first. A deploy never deletes your data.

Kept in your account

What exists, and the keys to it, are stored where you own them.

Mobile-first

The whole replicator fits in a pocket.

One hostname per engineer. A phone is a first-class client.

What it has made

The first project off the line.

BUILT WITH CLANKER.NET

clanker.engineer

Connected agents with shared context, tools and workflows.

A separate project. Based mode: hosted by us. Deployed mode: in your own accounts, set up together with us, by agreement. Its developer environments come out of a clanking machine.

Visit clanker.engineer

Modes

Two ways to run it.

A mode is how a project is run, never a property of a person. Both are available by agreement: a team asks, terms are agreed with us, and we switch it on.

Based mode

We operate it, in your own accounts. We run the control plane with access you grant and can revoke. Your code, keys and data stay in your accounts.

Deployed mode

It runs in your own cloud accounts, from your own repository, with our engine. You operate it. We hold nothing of yours.

Based modeDeployed mode
Who operates itWe doYou do
Where it runsWhere you choose (CLANKER.NET: your accounts; clanker.engineer: our hosting)In accounts you own
Who can sign inThe people you admit, with GitHubThe people you admit, with GitHub
UpdatesApplied by usPinned to a version you choose
What we holdOnly the access you grant (CLANKER.NET), or what it takes to run your workspace (clanker.engineer)Nothing

Want us to operate it in your accounts? Talk to us. For anything else, write to [email protected].

Get started

Start clanking.

Put your software factory to work.

Open the app

Want your own machine?

Read how it runs in your accounts