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.
joomiz init Use cases
What feature teams, platform teams and security teams can do with Joomiz: the jobs it is built for, from a first deployment to an audit.
Feature 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.
type: postgres Use a Kafka topic that another team owns
A consumed resource names the topic. The owning team keeps it, and your service gets access through the same plan.
type: kafka-topic Publish an API through Kong, with its consumers
Describe the endpoint and who may call it in the file. Each new consumer is one more entry, and a plan shows it first.
consumers: 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.
joomiz plan 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.
POST /apply Give every service the same deploy pipeline
The Cloud Foundry provisioner creates each service's Azure DevOps pipeline from one central template. Fix the template once, and every service gets the fix.
type: cloud-foundry-app Plan and apply from CI
A pipeline passes a token, and joomiz runs without an interactive login. Plan in the pull request, and apply after the review.
joomiz apply --token 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.
${{ …outputs.password }} Show who changed what
Every registration, apply and operator action names the person who did it. Operators read the whole trail with joomiz audit.
joomiz audit Apply to production only from a pipeline
A protected environment accepts an apply only from an approved pipeline identity, never from a laptop.
environments: prod Read enough?
Now try some of them yourself
The simulator walks you through four exercises: a new service, a fixed mistake, a database and an API on Kong. It runs in your browser, with no account.
Your use case is not here?
Tell us what your teams ship and what slows them down. We tell you what is possible today.