EJO runs your build, test, scan and deploy pipelines on agents inside your own network. See at a glance which commit is in which environment.
Docker, Maven, Helm or a preview per PR. Pick a template and bind it to your repo; parallel steps run at the same time, and the pipeline waits where an approval is needed.
You add a small .ejo file to each repo. EJO reads it, combines it with real deployments and fills in the service card itself.
The agent pulls jobs from the master itself; the agent always starts the connection. Secrets and source code never leave your network.
For every service you see the image running in each environment. When you promote, the same image moves to the next environment; nothing is rebuilt.
In production, shop is 3 commits behind staging
No. You can run builds and tests in EJO too, or keep your existing CI and leave only deploy and the catalog to EJO.
No. You build pipelines with a form, and variables like {{.ShortSHA}} show an example value next to them.
On agents in your own network. EJO Cloud only keeps the job queue, logs and approvals.
Yes. Install the master on your own infrastructure with the Helm chart or the offline install bundle.