Platform

One path to your cloud, and a person standing on it.

Every change reaches your infrastructure the same way: a typed spec, rendered to Terraform, planned against your own account, checked by policy, priced, and approved by a person. The assistant, the console, the API and your own agent are all editors over that one spec.
Get startedBook a walkthrough
the spec is the contractDesign rule
The model chooseswhich module, which parameters
The model neverauthors HCL
The model neverorders an apply
Validated againstthe provider’s own schema
Gated onplan, policy and a person

The platform

Everything between an idea and a running service.

Six parts, one desired state. Each is useful alone and they are designed to be used together.

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 OperateDrift, health, teardown and historyA team with nobody on call still needs answers on day two. SysJ keeps an inventory of every environment, notices when reality stops matching the plan, explains failed deployments, and tears things down safely when you are done.Learn more CostEstimates on every plan, and budgetsEvery plan carries a cost estimate next to the diff, so an approval is an approval of the bill as well as the change. Budgets per environment warn you before spend runs ahead of what you meant.Learn more GuardrailsPolicy, approval, permissions and auditEvery change, whether it came from the assistant, a form, the API or your own coding agent, becomes a Terraform plan. The plan is checked against policy, priced, and approved by a person before it is applied.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

The loop

Five steps, each producing something the next one reads.

Nothing is passed along as prose. Every step hands the next a structure it can check.

Describe

A conversation or a form produces a typed resource graph, checked against the regions, sizes and accounts your workspace actually has.

Render

The graph is rendered to Terraform mechanically and committed to your repository. The model never writes HCL.

Plan

Terraform plans against your account. Policy reads the plan and a cost estimate is attached to it.

Approve

A person reads the grouped diff and confirms. The approval is bound to that plan’s digest.

Apply and operate

The plan is applied in your account, Argo CD takes over deployments, and SysJ watches for drift from then on.

Architecture

Our control plane. Your cloud.

SysJ decides what should exist and asks you to approve it. Everything that exists runs in your account.

In SysJ

Conversationsyour workspace database
Desired statetyped resource graph
Plans and approvalsbound by digest
Activityappend-only log

In your accounts

Infrastructureyour cloud
Terraform stateyour bucket
Terraform and manifestsyour repository
DeploymentsArgo CD in your cluster

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