Skip to main content

Managed databases

Database as a Service (DBaaS)
Your production database, without needing an on-call DBA.

InteSys provisions, configures, secures, backs up and monitors your databases — from a single instance to a multi-region cluster — with data kept in Brazil. Your team owns the schema and queries; running the database is our job.

Request a proposal Speak with an expert
Learn more in the docs

We run the leading open source databases

  • MySQL MySQL
  • MariaDB MariaDB
  • PostgreSQL PostgreSQL
  • ClickHouse ClickHouse
  • CockroachDB CockroachDB
  • Valkey Valkey
  • Redis Redis
  • KeyDB KeyDB

Why DBaaS with InteSys

Everything a production database needs, delivered as a service.

Managed operations

Provisioning as Infrastructure as Code, updates, performance tuning and on-call. You get an endpoint and credentials; we handle the rest.

High availability by default

Replicas, automatic failover, an odd number of voters, anti-affinity and fencing before any promotion.

Backups with tested restores

Daily backups, point-in-time recovery and test restores on a schedule — not only in an emergency.

Data kept in Brazil

Primary, replicas, logs and backups in br-sp-1 (Cirion) and br-sp-2 (Equinix), under Brazil's LGPD.

Observability tied to on-call

Metrics, dashboards and alerts, with a runbook for every alert and a team that responds to it.

Handover documentation

You receive the topology, credentials, runbook and disaster recovery plan in writing.

Three tiers, one operation

Start at the tier your application needs today and move up later, without changing engine or provider and without rewriting the application.

Single instance

Development, staging, internal systems and smaller workloads.

One node on a VM or Kubernetes, in br-sp-1 or br-sp-2.

Daily backup, point-in-time recovery, monitoring and alerts.

Your application

Endpoint and its own credentials

Cirion — Cotia/SP

1 datacenter
Primary

Daily backup + PITR

Monitoring and alerts

Engines MySQLMariaDBPostgreSQLClickHouseCockroachDBValkeyRedisKeyDB

  • Daily backup

    with point-in-time recovery

  • Monitoring

    metrics and alerts

  • VM or Kubernetes

    in br-sp-1 or br-sp-2

  • Starting point

    grows without changing engine

High availability

Production that cannot stop on a host, disk or rack failure.

Primary and replicas in one datacenter, with automatic failover.

Everything above, plus a synchronous or semi-synchronous replica and fencing.

Your application

Endpoint and its own credentials

Automatic failover

Cirion — Cotia/SP

1 datacenter
Primary
Replica
Replica

Synchronous or semi-synchronous replication

Daily backup + PITR

Engines MySQLPostgreSQLClickHouseValkey

  • Automatic failover

    no manual intervention

  • Synchronous replica

    or semi-synchronous

  • Fencing

    before any promotion

  • Resilience

    to host, disk or rack failure

Multi-region

Critical production, contractual RPO/RTO and continuity across datacenters.

Replicas across br-sp-1 and br-sp-2, or a distributed database.

Everything above, plus a tested disaster recovery plan.

Your application

Endpoint and its own credentials

Cirion — Cotia/SP

Region 1
Primary
Replica

Equinix — SP3

Region 2
Replica
Replica
Cross-region replication

Tested DR plan

Engines MySQLPostgreSQLCockroachDB

  • Two datacenters

    Cirion and Equinix in SP

  • Tested DR

    plan and drills

  • RPO/RTO

    in the contract

  • Data in Brazil

    under the LGPD

The databases we run

Relational, analytical, distributed and in-memory. Other engines are evaluated case by case.

Relational, analytical and distributed

MySQLMariaDB

MySQL / MariaDB

Transactional OLTP, the most common choice in web applications.

PostgreSQL

PostgreSQL

OLTP with strong integrity requirements, extensions and advanced SQL.

ClickHouse

ClickHouse

Columnar analytics, aggregations over billions of rows.

CockroachDB

CockroachDB

Distributed, with local writes in several regions.

In-memory (NoSQL)

Valkey

Valkey

Cache, sessions, queues and counters. The open source (BSD) Redis fork and our default recommendation.

Redis

Redis

The same use, when the application depends on a specific Redis version or module.

KeyDB

KeyDB

Multithreaded, with active replication between nodes, for specific cases.

How ordering works

Each instance is sized and delivered by our team, not a self-service portal: the database starts life with the size, topology and protection the workload needs.

  1. Request

    Describe the application through the form or in a conversation with an expert.

    • Form
    • Expert

  2. Sizing

    Data volume, read/write ratio, peak concurrency and RPO/RTO decide the engine, tier and resources.

    • Data volume
    • Read/write
    • Concurrency
    • RPO/RTO

  3. Provisioning

    We build the instance as Infrastructure as Code, apply hardening, set up backup and monitoring, and validate with load and failure tests.

    • IaC
    • Hardening
    • Load test
    • Failure test

  4. Handover

    You receive the endpoint, credentials, documented topology, runbook and DR plan. From then on, operations are ours.

    • Endpoint
    • Credentials
    • Runbook
    • DR plan

  5. Ongoing operations

    Backup, monitoring, on-call and updates, with a runbook for every alert.

    • Backup
    • Monitoring
    • On-call
    • Updates
Operations measure, tune and feed back into sizing.

We don't replace your team — we cover the shift it can't.

Many customers have a strong development team and no DBA on call. InteSys takes on architecture, on-call and critical procedures; your team keeps ownership of the schema and queries.

Who looks after what

Your team

  • Application and business rules
  • Schema, indexes and schema migrations
  • Application queries

Agreed together

  • Least-privilege application users
  • RPO/RTO and maintenance windows

InteSys

  • Engine installation, configuration and updates
  • High availability and replication
  • Backups and tested restores
  • Monitoring, alerts and on-call
  • Hardening and administrative access
  • Infrastructure in br-sp-1 and br-sp-2
Request a proposal Speak with an expert

Frequently asked questions

What is Database as a Service (DBaaS)?

A database delivered as a managed service: InteSys provisions, configures, backs up, monitors and updates the instance, and your application reaches it through an endpoint with its own credentials. Your team looks after the schema and queries; operations are ours.

Can I start with a single instance and move to high availability later?

Yes. A single instance already comes with backup and monitoring. When the application grows, we add replicas and automatic failover, or a second region, without changing engine or provider. InteSys plans and carries out the change.

Which databases do you run?

MySQL/MariaDB, PostgreSQL, ClickHouse and CockroachDB, plus Valkey, Redis and KeyDB for in-memory data. Other engines are evaluated case by case.

Does my data stay in Brazil?

Yes. Primary, replicas, logs and backups stay in br-sp-1 and br-sp-2, under Brazil's LGPD. Data only leaves the country when the customer asks for it.

Who has access to the database, and how are backups tested?

Administrative access is restricted to the InteSys operations team; the application uses least-privilege users defined with your team. Test restores run on a schedule, not only in an emergency.

How does billing work?

Pricing depends on the sized resources (CPU, memory and storage), the service tier and backup retention. Request a proposal for your scenario.

Tell us about your application. We'll size and run the database.

Get a tailored proposal for your engine, service tier and backup retention.

Request a proposal Speak with an expert