Docs / Getting started
What is SysJ
SysJ builds Kubernetes clusters in your own AWS account from a plain description, shows you the real Terraform plan before anything is created, and tracks deployments to those clusters.
SysJ is an infrastructure platform for engineering teams without a dedicated DevOps function. You describe the cluster you need to the assistant or fill in a form, SysJ plans it with Terraform against your own AWS account, and nothing is built until a person approves that plan.
What you can do today
| Area | Available now |
|---|---|
| Cloud accounts | Connect an AWS account through a CloudFormation stack you create. |
| Clusters | Build, resize, inspect and tear down Amazon EKS clusters, from the assistant or the console. |
| Plans and policy | Every assistant change is a real terraform plan, checked against policy rules, that a person approves. |
| Delivery | Register repositories, applications and environments; request, approve, reject and roll back deployments. |
| Notifications | The bell in the console, email, and Slack or Microsoft Teams channels. |
| Workspace | Members, roles from 28 permissions, user import from a file, and an audit trail. |
The loop for infrastructure
- Describe the cluster to the assistant: cloud account, region, node size, node counts, Kubernetes version and what to install.
- SysJ runs
terraform planagainst your account. - Policy reads the plan and blocks anything it refuses.
- A person reads the changes, grouped by what they are for, and approves or rejects.
- SysJ applies exactly the plan that was approved, and shows each component as it comes up.
What stays yours
- Clusters run in your AWS account, and you pay AWS for them directly.
- Terraform state lives in an S3 bucket in your account, created by the stack you launch.
- SysJ reaches your account through an IAM role you create, and you can delete it at any time.