Describe your infrastructure.SysJ builds it.
A plain-English request becomes a Terraform plan in your own AWS, Google Cloud or Azure account. Policy checks it, a cost estimate prices it, and a person approves the real diff before anything is built.
Works with the tools your team already uses
- AWS
- Google Cloud
- Azure
- Terraform
- Kubernetes
- Argo CD
- Bitbucket
- Claude Code
- Cursor
- Slack
- PagerDuty
How it works
One path from a sentence to your cloud.
Every change takes the same six steps, whether it starts in a conversation, a form, the API or your own coding agent.
- DescribeA sentence, or a form
- GraphTyped, schema-checked
- PlanTerraform, in your account
- PolicyUnsafe changes refused
- ApproveA person, on the real diff
- ApplyBuilt, then watched
Describe
Say what you need.
A staging cluster, a database for orders, a bucket for uploads. SysJ asks only what it cannot infer.
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.
Check
Policy reads the real plan.
Terraform plans against your account, and unsafe networking, identity and data settings are refused before anyone is asked.
Approve
Read it, price it, confirm it.
Changes grouped by purpose with the monthly cost beside them. Your confirmation is bound to that exact plan.
Ship
Deploy through GitOps.
Argo CD in your cluster syncs from your repository. Environments promote in order; production waits for approval.
Operate
Know when reality drifts.
A change made in a cloud console is surfaced, never silently reverted. You adopt it or revert it, as a plan.
The platform
Everything between an idea and production.
Provision, approve, deploy and operate, in one place, over one desired state.
Ask in plain English.
SysJ asks the questions that matter and picks sound defaults for the rest.
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.
Refused before it runs.
Policy reads the real plan and stops unsafe changes.
The price, before you approve.
Every plan carries a monthly estimate beside the diff.
Approve the exact plan.
Changes grouped by purpose, bound to the digest you confirmed.
Ship through GitOps.
Argo CD in your cluster, manifests in your repository, promotion in order.
Drift, surfaced.
A change made in a console is shown to you, never silently reverted.
Yours to keep
Your cloud. Your code. Your keys.
Terraform in your repository, state in your bucket, workloads in your cluster, access through a role you can delete. Leave any time with a normal setup, not an export.
Why SysJ
Terraform is not the hard part. Being sure is.
What a small team cannot easily get is confidence that the change about to run is the one it meant, what it will cost, and a record of who agreed to it.
No wall of HCL
A team without a Terraform specialist gets a plan grouped by purpose, not a diff it was trying to avoid.
Approvals you can read
Every plan is grouped, priced and checked by policy before anyone is asked to agree to it.
Gated on the plan
What an AI says it will do and what the plan says are different things. SysJ gates on the plan.
Two ways to drive it
Our assistant, or your agent.
Use the assistant built into SysJ, or connect Claude Code or Cursor over MCP. The guarantees are the same either way.
The SysJ assistant
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.
Your coding agent, over MCP
Security
Built so your cloud stays yours.
SysJ acts through access you grant and can revoke, and nothing it proposes reaches your cloud without policy and a person.
No long-lived keys
Delegated access on every cloud, assumed for the length of a run.
A database per workspace
Your data is physically separate from every other customer’s.
Server-side permissions
Checked on every request, deny by default, revoked on the next click.
Policy on every plan
Unsafe networking, identity and data settings refused before approval.
The model never applies
An AI can propose a change. Only an approved plan can make one.
An append-only record
Every request, approval and change, in one log nobody edits.
Who it is for
Made for small teams shipping real products.
Questions
What teams ask first.
- Does SysJ need access keys to our cloud?
- No. You grant SysJ a role in your account, or the equivalent federated identity on Google Cloud and Azure. SysJ assumes it for the length of a run and stores no long-lived credential. Deleting the role ends access without asking us.
- Which clouds does SysJ support?
- Amazon Web Services, Google Cloud and Microsoft Azure, through the same describe, plan, approve and apply loop on each.
- Does the AI write our Terraform?
- No. The model chooses modules and parameters inside a typed resource graph. Terraform is rendered from that graph by code, validated against the provider’s schema, and planned for real before anyone approves it.
- Do we need Terraform or Kubernetes experience?
- No. SysJ is built for teams without a DevOps specialist. The plan is shown grouped and in plain language, and the raw Terraform is there for anyone who wants it.
- What happens to our infrastructure if we stop using SysJ?
- It keeps running. The Terraform is in your repository, the state is in your bucket, and Argo CD runs in your cluster. You leave with a normal setup rather than an export.
- How is SysJ priced?
- By the number of environments you manage, not by seats. The assistant is included, and asking for a plan is never billed.
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.