Administration
Cloud, on-prem and hybrid compared
The three ways to run Yavaren side by side: who runs what, where your data lives, what leaves your network, and how a new product is built and deployed in each.
Yavaren can be run three ways. Every feature works in all three; what changes is who runs each part and where your code and data are. The page Your setup shows which one you are on, with your current settings filled in.
You are on on-prem: your organisation runs Yavaren in its own environment.
Side by side
| Yavaren cloud | Hybrid runners | On-prem | |
|---|---|---|---|
| Who runs the control plane (console, API, job queue) | Yavaren | Yavaren | You |
| Where engineers work on your code (the runners) | Yavaren's runners | Your network, calling out to Yavaren | Your network |
| Where your projects, jobs, documents and logs are kept | Yavaren cloud | Yavaren cloud | Your database and document store |
| Where your credentials are | The secret store of Yavaren's runners | Your own secret store | Your own secret store |
| What reaches Yavaren | Everything the platform needs to run your work | Job results and redacted logs from your runners; never your credentials | Depends on how the installation is linked (below) |
| Updates, backups, scaling, security patches | Yavaren | Yavaren for the control plane, you for the runners | You (Yavaren publishes the releases) |
| Licence | Not needed | Not needed | A signed licence from Yavaren |
| Paying | Card or invoice | Card or invoice | Invoice, from the usage your installation reports |
How an on-prem installation is linked to Yavaren
| Connected | Restricted | Air-gapped | |
|---|---|---|---|
| Licence | Refreshed over the link | Refreshed over the link | A signed file you install |
| Updates | Version check and signed corrections over the link | The same | A signed file you import |
| Usage for invoicing | Sent monthly, without customer content | The same | A signed statement you send by hand |
| Learning data | Sent at the level your organisation chose | Kept here | Kept here |
| Health heartbeat | Versions, licence, component health, readiness, drift (never a secret value) and counts; counts and details can be switched off | Versions, licence, component states and readiness counts only | Off |
| Yavaren support acting on it | Only allowed actions, signed by Yavaren, in a session your administrators approve, or with full remote management they consented to | Only during a session your administrators opened | Never over a link: signed diagnostics files your administrator imports by hand |
| Anything else | Only what you switch on (summaries, mail relay) | Nothing | Nothing at all |
A new product in each
Every step of a new product is the same in all three: Yavaren asks its questions before each phase, drafts the business brief with its diagrams, then the features and the stories; the people you named approve each step. Then it sets up the repository and the CI/CD pipeline, and deploys once an approver says so.
| Step | Yavaren cloud | Hybrid runners | On-prem |
|---|---|---|---|
| Questions, brief, diagrams, features, stories | Drafted on Yavaren's runners | Drafted on your runners | Drafted on your runners; diagrams are drawn inside your installation |
| Repository | Created with the access you give, on your repository host | The same | The same, on your repository host (cloud or self-hosted) |
| CI/CD pipeline | Generated into your repository as a draft pull request a person merges | The same | The same |
| Deployment | Runs in your own pipeline, with your own cloud identity, after an approver approves | The same | Runs in your pipeline on CI runners inside your network, to your Kubernetes or servers |
| Who holds cloud credentials | Never Yavaren: your pipeline uses your identity | The same | The same |
Moving from one to another
Moving is a step you take with Yavaren, not a switch. An administrator asks on the Deployment card; Yavaren answers and agrees the plan with you. For on-prem, work through the readiness checklist under Your setup first: where it runs, network, secret store, database, runner sizing and how it links to Yavaren.