For developers

Get the environment you need without learning Terraform first.

Describe what your service needs, ship it through GitOps, and see why a deployment failed without opening a terminal. From the console, the API or your own coding agent.
Get startedBook a walkthrough
orders-api · releases · example
developmentv1.14.0 · synced
stagingv1.14.0 · synced
productionv1.13.2 → v1.14.0 · waiting for approval
preview · pr-212a41c9e0 · synced

Sound familiar

Where it goes wrong today.

Waiting on infrastructure

A new service needs a database and a queue, and the one person who knows how to create them is busy.

Copying YAML you do not trust

Manifests are copied from the last service and edited until they work, and nobody is sure which settings still matter.

Failures without explanations

A deployment fails and the first step is finding out where to look.

With SysJ

What changes.

Ask

Describe the service, get the infrastructure.

Tell SysJ what your service needs in a sentence. You get a plan to review and, once it is approved, a working environment with its connection details.

  • Databases, buckets, clusters and networking
  • Consistent defaults across every service
  • The Terraform in your repository to read or extend
assistant · example

You: We need a staging cluster for the orders API in eu-west-1.

SysJ: Will it serve customer traffic, or only your team? And should it be protected from deletion?

You: Team only. No protection needed.

SysJ: A two-node EKS cluster in a private network, reachable through your VPN. I have drafted the plan for you to review.

Ship

Push a branch, get a deployment.

SysJ builds your image and deploys it through Argo CD to the right environment. Pull requests get their own preview environment, removed when they merge.

  • Promotion from development to production
  • Rollback to any earlier release
  • Preview environments per pull request
orders-api · releases · example
developmentv1.14.0 · synced
stagingv1.14.0 · synced
productionv1.13.2 → v1.14.0 · waiting for approval
preview · pr-212a41c9e0 · synced

Automate

Use SysJ from the tools you already have open.

Call the API from CI, subscribe to webhooks, or connect SysJ to Claude Code or Cursor over MCP. Every change still goes through the same review.

  • REST API with workspace-scoped keys
  • MCP server for coding agents
  • Signed webhooks for every event
claude code · example
youadd a Postgres database for orders
agent → sysjpropose_change(environment: staging)
sysjplan +6 · policy passed · $64 / month
sysjwaiting for approval in SysJ

Read next

The parts of SysJ that matter most here.

ProvisionDescribe infrastructure in plain EnglishSay what you want in a sentence. SysJ asks the few questions that matter, builds a typed resource graph, and renders it to Terraform that plans against your own cloud account.Learn more DeployShip your code onto what SysJ builtConnect a repository, choose an environment, and SysJ builds the image and deploys it to your cluster through Argo CD, from manifests in your own repository. Promotion, approval and rollback included.Learn more API and MCPAutomate SysJ, or let your agent drive itEverything the console does is available through a documented API. Connect Claude Code, Cursor or any MCP client to SysJ, and every change it proposes still passes through the same plan, policy and approval.Learn more

See your own infrastructure as a plan.

Tell us about your team and the cloud you use. We will set up your workspace and walk through your first plan with you.

Get startedBook a walkthrough