Your database ready in minutes
Choose your engine and connect to a working database in minutes. Setup, backup, security and monitoring are on us; you focus on code and queries.
No setup fee · monthly billing · from $12/moCompute tier + as much disk as you use
Pick CPU and memory with a tier, and size the disk yourself by the GB. The entire disk you choose is yours — Tres covers the operating-system share.
What a managed database gives you
Choose the engine and size; your database is set up automatically and the connection details appear in the panel.
Optional daily automatic backups and a manual backup whenever you want; one-click in-place restore.
The database is closed by default; it only accepts connections from the IPs and CIDRs you allow.
See disk, CPU and memory usage in the panel; get an automatic alert as the disk fills up.
Scale compute up and down and grow the disk as needs change — with a short restart.
The current, maintained versions of each engine; we do not offer end-of-life (EOL) versions.
Choose the engine that fits your needs
Relational, document, or in-memory — each launches as a one-click managed instance on its latest versions.
The world’s most widely used relational database; the standard choice for web applications.
A MySQL-compatible, community-driven relational database; seamless migration and open source.
A powerful, standards-compliant relational database; complex queries and extensibility.
A document database; rapid development and scaling with a flexible schema.
A Redis-compatible in-memory store; for caching, sessions, and queues.
Need full-text search (OpenSearch, Elasticsearch) or event streaming and message queues (Apache Kafka)? Explore the Search and Queue service →
A running database in three steps
Setup, password generation, and security are on us. You connect within minutes using your standard client or your application’s driver.
# connect with your application’s driver mysql://user:password@host:3306/database # MySQL and MariaDB postgresql://user:password@host:5432/database mongodb://user:password@host:27017/database redis://:password@host:6379 # Valkey (Redis-compatible) # or with a client psql "postgresql://user:password@host:5432/database"
Leave the operations to us, keep control in your hands
Your data is kept on our own infrastructure, in the region you choose; it is never moved to another region without your permission. KVKK compliance in Türkiye regions.
The database comes closed to the outside; it is reachable only from the IPs and CIDRs you allow.
All of the disk you choose is yours — Tres covers the operating system’s share. You pay as you go.
Daily automatic and manual backups, one-click in-place restore; we protect your data.
Create your first database in minutes
No credit card, no commitment. A compute tier + pay-as-you-go disk — from $12/mo.
Start for freeWhat do teams using Managed Database say?
Managed Database (DBaaS) Guide
A database is the heart of most applications; yet keeping it running is one of the tasks IT teams spend the most time on. Between setup, version upgrades, backups, performance tuning, replication, failover, and 24/7 monitoring, database management keeps you from your real job — building the application. A managed database (DBaaS – Database as a Service) removes exactly this burden: the infrastructure, maintenance, and operations sit with the service provider; you simply take the connection details and focus on your queries. In this guide, we examine end to end what DBaaS is, the distinction between SQL and NoSQL, the database engines on offer (MySQL, MariaDB, PostgreSQL, MongoDB, Valkey), high-availability and security architecture, choosing the right database, and how Tres differentiates this service.
What Is a Managed Database (DBaaS)?
A managed database (DBaaS – Database as a Service) is a service model in which database setup, maintenance, backup, updates, scaling, and monitoring are handled by the cloud provider, while the user focuses solely on using the database. In the classic “run the database on your own server” model, operating-system installation, configuring the database software, security hardening, and backups are entirely your responsibility. With DBaaS, all of these operational layers move to the provider.
In common usage it is called database as a service or a managed database, and in the international literature DBaaS or managed database. Amazon RDS, MongoDB Atlas, and Google Cloud SQL are well-known examples of this model; Tres delivers the same experience on domestic, KVKK-compliant, pay-as-you-go infrastructure.
How Does DBaaS Work?
With DBaaS, you create a database instance from the panel or API with the engine and resource size you select; the service becomes active instantly and you are given connection details (an endpoint). Behind the scenes, the provider manages the hardware, replication, automatic backup, version updates, and monitoring. Your application accesses the database over this connection; you never deal with maintaining the database server.
The Difference Between DBaaS and Running a Database on Your Own Server (TCO Comparison)
The essence of the question “what is the difference between DBaaS and setting up a database on my own server” is who bears the responsibility and the total cost of ownership (TCO). On your own server you have full control, but the entire operational burden, expert time, and hidden costs are also on you. With DBaaS, operations move to the provider, setup drops to seconds, and scaling becomes easier.
| Criterion | Managed Database (DBaaS) | Database on Your Own Server |
|---|---|---|
| Setup time | Instant (panel/API) | Manual, hours–days |
| Maintenance and updates | Provider manages | Entirely on the user |
| Backup | Automatic, policy-based | User must set it up |
| High availability | With replication/failover | User must set it up |
| Scaling | Easy via resource increase | Hardware/configuration intervention |
| Need for an expert (DBA) | Low | High |
| Monitoring and alerting | Included | Must be set up separately |
| Cost model | Pay-as-you-go | Hardware + license + staff |
Tip: The cost advantage of DBaaS lies not only in hardware but in hidden operational costs. When you run your own database, the time a DBA spends on backup checks, version upgrades, and midnight failover interventions is invisible in most budget calculations. DBaaS eliminates this invisible cost.
The Difference Between SQL and NoSQL Databases
The first step in choosing the right database is understanding the distinction between SQL (relational) and NoSQL. The two are not rivals but solutions to different problems.
| Criterion | SQL (Relational) | NoSQL |
|---|---|---|
| Data structure | Tables, fixed schema | Flexible schema (document, key-value) |
| Example engines | MySQL, MariaDB, PostgreSQL | MongoDB (document), Valkey (key-value) |
| Area of strength | Data integrity, complex queries | Scale, flexibility, speed |
| Typical use | Finance, e-commerce, ERP | Real-time, content, cache |
| Transaction | Strong ACID support | Varies by model |
Relational databases are preferred in scenarios where the consistency and relationships of data are critical (payments, orders, accounting); NoSQL is preferred in scenarios where flexibility, horizontal scale, and low latency come to the fore (content, sessions, caching, real-time).
The Database Engines on Offer
The Tres managed database service offers a broad range of engines covering both relational (SQL) and NoSQL needs. The table below provides a quick comparison; each engine is then detailed.
| Engine | Type | Notable use | Strength |
|---|---|---|---|
| MySQL | Relational (SQL) | Web, e-commerce, CMS | Ubiquity, compatibility |
| MariaDB | Relational (SQL) | MySQL-compatible projects | Open source, performance |
| PostgreSQL | Relational (SQL) | Analytics, enterprise, geospatial data | Advanced queries, data integrity |
| MongoDB | NoSQL (document) | Modern applications, content | Flexible schema, scale |
| Valkey | NoSQL (in-memory) | Cache, sessions, queues | Low latency, speed |
The world’s most widely used open-source relational database. The standard choice for web applications, e-commerce, and content management systems (WordPress, WooCommerce, etc.); it stands out for its mature ecosystem and broad compatibility.
The open-source, community-driven fork of MySQL. While preserving MySQL compatibility, it offers performance and feature advantages in some workloads; it is a strong alternative for projects that value license independence.
An enterprise-grade relational database known for advanced query capabilities, JSON support, geospatial data (PostGIS), and high data integrity. It is preferred for complex queries, analytical workloads, and applications where data integrity is critical.
The most popular document-based NoSQL database. With its flexible schema, it is ideal for rapidly changing data models, content storage, real-time applications, and large-scale modern applications.
The high-performance, open-source alternative to Redis (a community fork under the Linux Foundation). Running in-memory, it is used in low-latency scenarios such as caching, session management, queues, and real-time counters. Valkey stands out for teams seeking an open-source, sustainable alternative to Redis after its license changes.
Alongside the managed database, services such as OpenSearch for full-text search, Kafka for event streaming and message queues, and Redis for caching and messaging are also offered as part of the “Search and Queue” solutions. This lets you build your entire data layer on a single platform.
High Availability, Replication, and Backup
In an enterprise database, the real issue is not that it “runs,” but that it runs without interruption and without data loss. Tres managed database provides this assurance across multiple layers:
- Replication: Data is copied from the primary node to one or more replicas; the read load is distributed and a replica stands ready against failure.
- Failover: When the primary node fails, the service is automatically redirected to a replica node; downtime is minimized.
- Automatic backup: Policy-based scheduled backups provide continuity against human error and data loss.
- Point-in-Time Recovery (PITR): The ability to return to a specific point in time; the option to restore accidentally deleted or corrupted data to its state before the incident.
- Monitoring and alerting: Database performance and health are continuously monitored; early warnings are issued on anomalies.
Tip: Backup and high availability are different things. Replication and failover prevent downtime; backup and PITR prevent data loss. In an enterprise architecture, the two should be designed together — one is no substitute for the other.
Database Security and KVKK Compliance
The data layer is the most sensitive part of an application; DBaaS security is not limited to passwords alone. In Tres managed database, security is handled across multiple layers:
- Network isolation (VPC): Reducing the attack surface by closing the database to the internet and placing it on a private network that only application servers can reach.
- Access control: Preventing unauthorized access through user-based authorization and strong authentication.
- Encryption: Data security through an encrypted connection during transmission (in-transit).
- KVKK and data residency: When a Türkiye location is selected, personal data is hosted domestically; regulatory compliance is made easier.
- Backup security: Keeping backups as protected, policy-retained, independent copies as well.
In regulated sectors such as finance, healthcare, and e-commerce, isolating the data layer and KVKK compliance are not a preference but a requirement; DBaaS can be configured to meet these requirements from the outset.
Which Database Should I Choose? A Scenario-Based Guide
The answer to “which database should I choose” lies in your workload. Common scenarios:
- E-commerce / orders / payments: Data integrity is critical → PostgreSQL or MySQL/MariaDB. Add Valkey (cache) alongside for cart and session.
- Content management / WordPress / CMS: MySQL or MariaDB.
- Analytics / complex queries / geospatial data: PostgreSQL.
- Modern application / flexible schema / mobile backend: MongoDB.
- Cache / sessions / real-time counters / queues: Valkey.
- Full-text search: OpenSearch (Search and Queue).
- Event streaming / microservice messaging: Kafka (Search and Queue).
Most modern applications use not a single engine but a combination: for example, PostgreSQL (primary data) + Valkey (cache) + OpenSearch (search) working together. Because Tres offers them all on a single platform, you can build this architecture with a single provider.
What Makes Tres Managed Database Different?
MySQL, MariaDB, PostgreSQL, MongoDB, and Valkey on a single platform; SQL and NoSQL needs together.
A current, sustainable option for teams seeking an open-source alternative to Redis.
Thanks to our own platform, a database instance is ready to use instantly.
Management integrated into automation; the ability to manage infrastructure in natural language with AI assistants.
Pay only for what you use; KVKK-compliant Türkiye plus Sofia/Frankfurt for European reach.
Managed database in the same ecosystem as Search and Queue (OpenSearch, Kafka, Redis), block/object storage, and backup.
Frequently Asked Questions (FAQ)
What is a managed database (DBaaS)? +
A managed database (DBaaS) is a service model in which database setup, maintenance, backup, updates, and scaling are handled by the cloud provider. The user simply uses the database and does not deal with server operations.
What does DBaaS mean? +
DBaaS is the abbreviation of the phrase “Database as a Service.” It describes the model in which a database is offered as a cloud service.
What is the difference between SQL and NoSQL? +
SQL (relational) databases offer a fixed schema and strong data integrity; MySQL, MariaDB, and PostgreSQL are examples. NoSQL offers a flexible schema, scale, and speed; MongoDB (document) and Valkey (in-memory) are examples. The choice depends on the structure of your data and your workload.
Which database engines are offered? +
The Tres managed database service offers MySQL, MariaDB, PostgreSQL, MongoDB, and Valkey. In addition, OpenSearch, Kafka, and Redis are provided as part of the Search and Queue solutions.
What is the difference between MySQL and MariaDB? +
MariaDB is the open-source community fork of MySQL and is largely compatible with it. It offers performance and feature differences in some workloads; projects that value license independence may prefer MariaDB.
What is Valkey, and how does it differ from Redis? +
Valkey is the open-source, community-driven alternative to Redis (developed under the Linux Foundation). It is an in-memory data store used for caching, session management, and low-latency operations. It is preferred by teams seeking open-source continuity after Redis’ license changes.
When should PostgreSQL be preferred? +
PostgreSQL stands out in analytical and enterprise applications that require complex queries, strong data integrity, JSON, and geospatial data (PostGIS).
Which projects is MongoDB suitable for? +
MongoDB is suitable for rapidly changing data models that require a flexible schema, document-based content, and real-time modern applications.
Which database should I choose? +
The choice depends on your workload: if data integrity is critical, PostgreSQL/MySQL/MariaDB; if you need a flexible schema, MongoDB; for caching and low latency, Valkey. Most applications use these together (for example, PostgreSQL + Valkey).
How quickly does a managed database become active? +
On the Tres platform, a database instance becomes active instantly. When you create it from the panel or API, it is ready to connect within seconds.
Is backup included with DBaaS? +
Yes. Policy-based automatic backup is provided; it offers continuity against data loss and erroneous operations.
What is Point-in-Time Recovery (PITR)? +
PITR is the ability to roll a database back to a specific point in time in the past. In the event of accidental deletion or data corruption, it provides the ability to return to the state just before the incident.
Is the database highly available? +
High availability can be achieved with replication and failover architectures, so the risk of a single point of failure stopping the service is reduced.
What are replication and failover for? +
Replication copies data to replica nodes and distributes the read load; failover automatically redirects the service to a replica when the primary node fails, minimizing downtime.
Can the database be managed via API? +
Yes. Database creation, backup, and management operations can be performed via the REST API and integrated into automation processes. With MCP support, natural-language management through AI assistants is also possible.
Can I migrate my existing database to Tres? +
Yes. Your existing database can be moved to the Tres managed database service using suitable migration methods; team support is provided during the move to the cloud.
How is database security ensured? +
Multi-layered security is provided through network isolation (VPC), user-based access control, in-transit encryption, and protected backups. A Türkiye location makes KVKK and data-residency compliance easier.
Is my data kept in Türkiye? +
When a Türkiye location is selected, data is hosted domestically in compliance with KVKK and data residency. Sofia and Frankfurt locations are also available for projects serving Europe.
How is DBaaS cost calculated? +
Tres works on a pay-as-you-go model; you pay only for what you use, based on the engine you select, the resource size, and the usage duration.
Can I increase database resources later? +
Yes. Resources can be increased as your data and traffic grow; thanks to the managed setup, scaling is far easier than on your own server.
Are OpenSearch, Kafka, and Redis part of the database service too? +
These services are offered as part of the Search and Queue solutions. OpenSearch is used for full-text search, Kafka for event streaming and message queues, and Redis for caching and messaging; they sit on the same platform alongside the managed database engines.
Does DBaaS make sense for small projects too? +
Yes. Thanks to the pay-as-you-go model, you start small and scale as you grow. The advantage of high availability and automatic backup without building a DBA team is especially valuable for small teams.
How do I connect to the database? +
When your database is ready, the host, port, username, password, and a ready-to-use connection string appear in the panel. You connect using standard clients (mysql, psql, mongosh, redis-cli) or your application’s driver.
Is external access to my database secure? +
Your database is completely closed to the outside by default. From the panel, you open access by adding only the IPs or CIDRs you trust; all remaining traffic is blocked at the firewall.