What we run, and what you own

What this means

What this means

This is a managed machine, not managed code. We are responsible for the machine and everything that keeps it serving; you are responsible for the application running on it and how it behaves.

Before you start

Before you start

Nothing to prepare — this article exists so there is no argument later about who was meant to do what.

Step-by-step guidance

Step-by-step guidance

1. We own the virtual machine, its operating system and its patches.
2. We own the JDK: installing it, and keeping it current within the version you pinned.
3. We own the build-and-deploy pipeline that turns your repository into a running process.
4. We own the TLS certificate and its renewal.
5. We own the backups and the monitoring, and we are the ones woken when the machine stops serving.
6. You own your application: its code, its dependencies, its migrations and its correctness.
7. You own your JVM tuning — heap sizing, garbage collector choice, thread pools.
8. You own what your application talks to, including any database it uses.

What CM Cloud support will review

What CM Cloud support will review

If you are unsure which side of the line a problem sits on, ask. Support will look, and will tell you plainly if it turns out to be in your application rather than passing it back without explanation.

What is not automated yet

What is not automated yet

We do not profile your application, tune your queries, or change your code. We can tell you what the machine was doing when something went wrong, which is usually enough to find the rest.