CLANKER.NET

Deploy your own clanking machine.

A clanking machine is a factory for the working environments your team needs, on infrastructure you own.

Open the app See how it works

What it makes

Working environments, made to order.

A host in your accounts

One machine in your cloud account that runs everything.

A workspace per engineer

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

A coordination gateway

Where engineers and their agents hand off work.

How it works

Three steps.

  1. 01

    Describe your product

    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.

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

    Your team works in it

    Every engineer gets a workspace with your product running, on your domain over your private network, plus the gateway.

    ssh [email protected]

What it has made

The first product off the line.

BUILT WITH CLANKER.NET

clanker.engineer

An AI-agent workspace: shared memory, sessions, skills and connectors for any coding agent, and an operator app on your phone.

Its developer environments, staging and production all come out of a clanking machine.

Visit clanker.engineer

Deployed mode

Your accounts. Your machine.

Bring your own cloud: your machine comes up in accounts you own, from your own repository. We hold nothing of yours.

Runs in your accounts

Compute, network, names and secrets stay yours.

Starts from your repository

One file, one workflow, run by your own CI under your permissions.

Nothing held by us

No credentials, no way in, no telemetry.

Get started

Start clanking.

The app is where your team sees its machines.

Open the app

Want your own machine?

Deployed mode