Feature teams
Start a new service on the golden path
joomiz init writes the file and register adds the service. The first plan shows the whole environment before anything exists.
Your platform team builds the golden path. Feature teams ship on it.
A feature team describes what a service needs in one file, in its repository. Joomiz checks the file against your platform team's rules and plans every change before it is applied.
or write to sales@joomiz.com
application:
name: inventory-api
golden-path: java-web-application
environments:
test:
deployments:
- id: inventory-api-test
type: cloud-foundry-app
env:
DB_PASSWORD: "${{managed-resources.db.outputs.password}}"
managed-resources:
- id: db
type: postgres
db (created): Would create 'db' (postgres).
inventory-api-test (updated): Would update.
env.DB_PASSWORD: (known after apply)
plan succeeded. Nothing was changed.
- Every change is planned first apply refuses a file that was not planned.
- Secrets stay in your vault Files and plans hold references, never values.
- Each team owns its services A team acts only on its own applications.
- Bring your own building blocks Provisioners follow an OpenAPI contract.
How it works
Three commands, in this order
The same three steps for every change, from the first deployment to a new database.
joomiz validateChecks the file against your platform team's rules and reports every problem. It changes nothing. Checks the file. Changes nothing. joomiz.yaml is validjoomiz planShows what would change in one environment, and what drifted. It changes no infrastructure. Shows what would change. Changes nothing. plan succeeded. Nothing was changed.joomiz applyMakes the change. It refuses a file that was not planned for that environment. Makes the change, only from a plan. apply succeeded
No account, no installation
Try it now, in your browser
Validate, plan and apply a small service in a simulated terminal. Edit the file and see the same checks as in VS Code. Watch the application appear in test.
Try it now Nothing on the page calls a real control plane.
Use cases
What teams use Joomiz for
What feature teams, platform teams and security teams can do with Joomiz.
See all use casesFeature teams
Get a database without a ticket
Declare a postgres resource next to the code. The plan shows it, apply creates it, and the password stays in your vault.
Platform teams
See drift before you apply
plan asks each provisioner what really exists. A change made outside Joomiz appears in the plan, not as a surprise in production.
Platform teams
Turn your automation into a provisioner within your rules
A provisioner is a small service behind an OpenAPI contract. Put a script, a pipeline or a cloud API behind it once, and every team can use it.
Security and compliance
Keep secrets out of repositories
The file holds references, never values. The control plane refuses a sensitive output that is not a vault reference.
Security and compliance
Show who changed what
Every registration, apply and operator action names the person who did it. Operators read the whole trail with joomiz audit.
For each team
What changes for each team
Feature teams
- One file in your repository.
- Check it before you push, and preview every change.
- VS Code shows problems and completion as you type.
Platform teams
- Define the rules and the building blocks once.
- A building block is a type plus a provisioner.
- Every change goes through the same rules.
Architects
- The file states the result. The control plane owns the state.
- Each building block has a closed schema.
- Provisioners follow an OpenAPI contract.
Engineering managers
- Every service names its golden path.
- A team acts only on its own applications.
- An audit trail names who applied each change.
FAQ
Questions we hear
Short answers about what Joomiz is, what it is not, and how it fits next to the tools you already use.
Read the FAQIsn't this just Terraform?
Joomiz borrowed the plan and apply steps from Terraform on purpose. Terraform is a tool for describing infrastructure in code.
How is this different from a developer portal like Backstage?
Backstage is an open-source framework for building a developer portal. Joomiz is not a portal.
Does Joomiz see our passwords?
A joomiz.yaml file never holds a secret. A provisioner stores a secret, such as a database password, in a vault.
Talk to us
Tell us about your platform and the services your teams ship.