Home Databases Managed databases explained

Managed databases explained

Last updated on Jul 14, 2026

A managed database gives you a database engine that Gewape Cloud runs, patches, monitors and backs up. You look after your data and your queries; we look after the server, the operating system, and the engine underneath. You manage these under Databases in the console.

Why use one

Running a database well means installing the engine, tuning it, keeping it patched, and setting up reliable backups. A managed database does all of that, so you get a ready endpoint to connect to and can focus on your application. You choose the engine, the version, the size, and the storage; we handle the rest.

Managed or self-run?

  • Managed (this): least maintenance. Good for almost everyone. Backups, patching and monitoring are built in.
  • Self-run: install an engine yourself on a Cloud Server with an attached volume. Full control, but every bit of maintenance is yours. Choose this only when you need something the managed option does not offer.

The pieces

  • An instance is the running database server, with its engine, size, storage and a connection endpoint.
  • Databases and users live inside an instance.
  • Backups are saved copies you can restore from.

How to