Skip to content

Your infrastructure, connected

Your infrastructure.
One clear view.

From the first deploy to your next big idea. Connect your machines, ship your apps, and keep everything in sight. All from Mesa.

Your machines. Your projects. Your call.
mesa / console

Workspace / production

Looking good from here.

Connected
Servers03
Applications08Running
Workspaceproduction
Your applications 3 of 8
webDocker containerRunning:3000
apiDockerfile appRunning:4000
postgresShared serviceRunning:5432
Last connection check successful

Deployment complete

web · production · receipt saved

Just now
A look inside Mesa. Example workspace shown.

Bring your own infrastructure

Connect the machines you already own.

A plan before every apply

Review deployment changes before they run.

One control plane. Your way in.

A web console, JSON API, and MCP access.

01 From machine to momentum

Less piecing it together.
More putting it out there.

Mesa brings the moving parts into one workflow, so you can spend more time on what you’re building.

  1. 01 Connection verified

    Connect your machine

    Add a MesaBin service URL and token. Mesa discovers the commands and capabilities available on that machine.

  2. 02 Deployment plan ready

    Make a plan. Ship your app.

    Start with a container, Dockerfile, or Compose stack. Choose a destination, review the plan, and apply when you’re ready.

  3. 03 Every run has a record

    Keep the whole picture

    Check applications, inspect logs, manage workspaces, and follow command results without losing your server context.

02 A place for every moving part

Everything within reach.
Nothing out of your hands.

From an individual service to a multi-machine setup. The tools you need, with the details still visible.

Deploy with intention

From blueprint to running app.

Import your project, pick a reusable VM destination, and review a deployment plan pinned to a specific revision.

production / deployment planReady
+webCreate container
~apiUpdate revision
Review first. Apply when ready.

Separate machines.
Connected thinking.

Discover peer servers, configure reciprocal routes, and bind endpoints across nodes from the same workspace.

app-01 data-01

The right access.
For the right people.

Citadel sign-in, per-server viewer and operator roles, and personal API tokens with scoped permissions.

D

Developer

Operator
T

Teammate

Viewer
Built for your workflow

A console for you.
An API for everything else.

Use the browser, connect a CLI, or give your tools MCP access. The same actions and permissions power every interface.

# Your infrastructure, one request away

GET /api/v1/servers Authorization: Bearer YOUR_PERSONAL_TOKEN
JSON:APIOpenAPIMCPOne permission model

Preview data is illustrative. Available operations follow each connected machine’s capabilities.

03 From the same studio

Built by people
who build things.

Mesa comes from Combine, the independent software studio behind Cablebox. We make tools that bring the complicated parts of work a little closer together.

Meet Combine
Also from Combine
Cablebox

Switch project. Everything follows.

Chat, tasks, whiteboards, and calls. One place for the people behind your projects.

04 Good questions

A little more clarity.

Something else on your mind?
Talk to the people building Mesa.

What is Mesa, exactly?
Mesa is a web control plane for machines running MesaBin. It brings server connections, application commands, deployment plans, networking, and run history into one interface. MesaBin runs on your machines and does the actual work.
Do I need to move my infrastructure?
You connect your own machines by adding their MesaBin service URL, token, and project alias. Mesa works with the capabilities each machine exposes, so you can manage them from one place.
What can I deploy?
Start with a web container, a Dockerfile application, or a Compose stack. Managed deployments support project imports, versioned blueprints, and reusable VM destinations on machines with the corresponding MesaBin capabilities.
Can I use Mesa with scripts and AI tools?
Yes. Mesa exposes a JSON API and an MCP endpoint backed by the same actions and access policies as the web console. Create a scoped personal API token from your account to connect your tools.
How do I get started?
Sign in with Citadel. A server administrator can then connect a MesaBin machine and grant your account access. If you need help setting up Mesa for your team, get in touch with us.

Less friction. More forward.

Your next deploy
starts here.

Bring your machines. We’ll bring a little clarity.