Application database
An environment matched to your database engine and workload. We manage resources, secure access and the connection to your application.
Databases under our care.
Managed databases for applications and businesses.Infrastructure, security and recovery in one subscription.We monitor databases and respond to outages.
Choose your level of careData your business depends on.
From a single application database to an environment with many dependencies.We match resources to the workload and care to the importance of your data.
More data and traffic
Your database grows, traffic increases or queries slow down. We investigate the cause and identify changes to configuration or resources.
Protected data
Permissions, secure access and regular backups. We prepare for data recovery after an outage or an unintended change.
A key business process
A database supports daily work and key business operations. We agree how incidents are handled and how data is recovered.
Choose your level of care.
We provide a managed environment or take over your database at its current provider.The level of care defines response coverage, recovery and the monthly support allowance.
Standard
Ongoing care for your application database: secure access, stable operation and tested data recovery.
from PLN 499
excl. VAT / month1 h total support each month
- Infrastructure and database administration
- 14-day backups and 7-day PITR
- Quarterly recovery test
Business
For a business that relies on its database: faster response, more frequent checks and a larger support allowance.
from PLN 999
excl. VAT / month3 h total support each month
- Critical outage: response within 30 min during office hours
- 14-day PITR and performance review
- Monthly recovery test
Bespoke
For complex databases needing larger resources, replication and a tailored service continuity plan.
Scope quotation
Resources and scope of careDefined in the project
- Resources matched to the workload
- Replication and service availability
- Agreed recovery plan
Base profile: 2 vCPU · 8 GB RAM · 80 GB NVMe. One PostgreSQL, MySQL or MariaDB node. The volume holds the operating system, data and logs. Before launch, we confirm data size, write rate and backup space. Larger resources are selected independently of the care level.
We offer the same care levels for Microsoft SQL Server, with a separate calculation for infrastructure and licences. Larger resources and high-availability architecture are priced to your needs.
Your database under ongoing care.
Resources, the database engine and support form one managed service.We maintain your database and an agreed path to recover its data.
Engine and performance
A stable foundation.
We maintain the database engine and monitor resource use. We diagnose load, connections and queries that affect application performance.
Access and protection
Data under control.
We configure database access and permissions. We update the environment in agreed maintenance windows and check that it works after each change.
Backups and recovery
A tested recovery path.
We keep backups off the database host and check their results. We test data recovery and the continuity of logs needed for PITR.
Diagnosis and incident handling
Someone owns the problem.
We investigate outages and restore the database under our care. We check application dependencies and agree on any further corrective work.
The right engine for your data.
Choose the care level for your business needs.We match technology, resources and licences to the application.
PostgreSQL
Applications and relational data.
Engine maintenance, access, backups and data recovery. Before taking over, we check the version, extensions and dependencies of your application.
MySQL and MariaDB
Websites and web-based systems.
We select a compatible engine version and environment configuration. We manage connections, performance, backups and data recovery.
Microsoft SQL Server
Business software and processes.
We match the edition, resources and licensing model to the application. Infrastructure, care and paid licences are presented in one quotation.
Other database engines
Scope matched to the use case.
We assess MongoDB, Redis/Valkey and other engines before taking them on. We agree on maintenance, data persistence and environment recovery.
¹ Entry prices apply to a PostgreSQL, MySQL or MariaDB profile after workload assessment. For Microsoft SQL Server and other engines, we confirm the price, version, licences and available recovery options separately.
Compare what is included.
Every plan maintains the database we have accepted into care.Plans differ in response coverage, recovery and the monthly support allowance.
The base profile and entry prices apply to PostgreSQL, MySQL or MariaDB after workload assessment. For Microsoft SQL Server and other engines, we separately confirm the price, version, licences and available recovery options.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Base profile | 2 vCPU · 8 GB · 80 GB NVMe | 2 vCPU · 8 GB · 80 GB NVMe | Matched to the environment design |
| Total monthly support | 1 h per month | 3 h per month | An agreed work allowance |
| Backups and retention | 14-day backups · 7-day PITR | 14-day backups · 14-day PITR | Policy based on requirements |
| Recovery test | Quarterly | Monthly | As agreed in the plan |
Engine, resources and performance
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Engines in the base profile | PostgreSQL, MySQL, MariaDB¹ | PostgreSQL, MySQL, MariaDB¹ | Engine and edition after assessment |
| Microsoft SQL Server | Infrastructure and licences quoted separately | Infrastructure and licences quoted separately | Edition, resources and licences matched to the design |
| Other database engines | Scope and price after assessment | Scope and price after assessment | Engine and architecture matched to the design |
| Processor and memory | Base profile or larger | Base profile or larger | Workload-based sizing |
| Data storage | NVMe sized for the profile | NVMe sized for the profile | Capacity and performance sizing |
| Query diagnostics | Analysis of a reported issue | Analysis and priority handling | Scope for the whole environment |
| Expansion and replicas | Expansion by agreement | Expansion by agreement | Replicas and HA architecture |
Access and updates
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Database access | Agreed network and permissions | Agreed network and permissions | A model for the whole environment |
| Engine updates | Agreed maintenance windows | Change plan and dependencies | Process based on requirements |
| Post-change checks | Database and application connection | Database and agreed application paths | Agreed acceptance scenarios |
Monitoring, backups and recovery
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Automated monitoring | 24/7: database, resources and backups | 24/7: database and dependencies | Coverage of the whole environment |
| Engine-level backup | Daily · 14-day retention | Daily · 14-day retention | As defined in the data policy |
| Recovery method | Backup and PITR up to 7 days back | Backup and PITR up to 14 days back | As defined in the recovery plan |
| Recovery test | Quarterly, included | Monthly, included | As scheduled |
| Recovery objectives | Agreed before launch | Agreed before launch | Based on architecture and tests |
Administration and support requests
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Office hours | Mon–Fri, 9 am to 5 pm (Warsaw) | Mon–Fri, 9 am to 5 pm (Warsaw) | Agreed support windows |
| Total monthly support | 1 h each month | 3 h each month | An allowance matched to your needs |
| Time allowances | Unused hours do not roll over | Unused hours do not roll over | Following the agreed model |
| Maintenance and backup tests | Within the shared support allowance | Within the shared support allowance | As defined in the service scope |
| Critical outage response | Within 4 business hours | Critical outage: within 30 min during office hours | Response and on-call cover by agreement |
| Outside office hours | Subject to support availability | Priority handling, subject to availability | Agreed on-call cover |
| Review and report | Database maintenance checks | Monthly: performance and recommendations | Agreed report scope and frequency |
| Additional administration | PLN 300 excl. VAT / h | PLN 300 excl. VAT / h | Following the agreed quotation |
Price and database onboarding
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Monthly subscription | From PLN 499 net | From PLN 999 net | Environment and care quotation |
| Migration and setup | Quoted separately before starting | Quoted separately before starting | Stages defined in the project |
| Paid licences | Depends on the chosen engine | Depends on the chosen engine | An environment licensing plan |
| Database in an application package | Review of existing coverage | Review of existing coverage | A combined service model |
What does care include?
Maintenance, checks and agreed changes share one monthly support allowance: 1 h in Standard and 3 h in Business. Automated backups, monitoring and tests do not count as additional staff time. The allowance renews monthly, and unused hours do not roll over.
Before taking over, we check the database condition, dependencies and recovery method. We agree on fixing existing issues or document the risks accepted by the client.
Response time means starting work on a critical outage that prevents use of the database.
We count from detection by our monitoring or receipt of a report through an agreed channel, whichever happens first.
The clock runs only during office hours: Monday–Friday, 9 am–5 pm Warsaw time, excluding Polish public holidays.
If an outage is detected or reported outside office hours, the clock starts when office hours next begin.
Repair time and recovery objectives are agreed separately. Monitoring runs 24/7; continuous on-call cover requires a separate agreement.
We size backups and logs for the database size and write rate. Required resources, backup capacity and the price are confirmed before launch.
PITR lets us restore the database to a selected time within the agreed window. Acceptable data loss and recovery time are based on the architecture and recovery tests.
Configuration changes and optimisations use the shared support allowance. Larger migrations or code restructuring are quoted before work begins. If the database is already covered by our application care, we account for the existing subscription.
We agree further work and any cost before exceeding the allowance; there is no automatic extra charge. Fixing an error caused by our change does not use the client’s hours.
Routine security and functional updates compatible with the accepted environment are included in care. A migration requiring a rebuild or repair of unsupported dependencies is quoted after assessment; a new version number alone does not trigger an additional charge.
The accepted application, database and machine are covered by one care scope. An additional subscription applies to new responsibilities or a separate environment.
Subscription and data handover
Monthly subscriptions with an onboarding fee have a one-month notice period. The option without an onboarding fee has a three-month notice period. We agree the scope of onboarding before the service begins.
Annual plans are paid for one year in advance. Renewal terms and the settlement of early termination are set out in the agreement before the service starts.
When the service ends, we hand over the files, database, code you own, configuration and start-up instructions. One plan covers the accepted environment and its components; we do not charge for the same database or machine again under a second subscription.
From review to ongoing care.
- 01
Database review
We check the engine, data, workload and application dependencies. We agree on access requirements and how your data will be recovered.
- 02
Preparation
We size resources, security and care for your needs. We plan migration, backups and checks to confirm correct operation after the move.
- 03
Ongoing care
We restore to an agreed time, check the data and application connection, and verify the recovery window. We then enable backup and log monitoring.
Questions about care.
How does PITR differ from a regular backup?
A backup restores the database to a saved state. PITR also uses change logs to restore it to a selected point in time.
For the base profile, Standard includes a 7-day window and Business a 14-day window. For Microsoft SQL Server and other engines, we confirm the recovery method and window after assessment.
RPO defines acceptable loss of recent data, while RTO defines the time to restore service; we confirm these objectives before launch.
Does the database need a separate subscription?
Not always. If it is already part of an application we maintain, we first review the scope of existing care.
We quote separately for additional resources and responsibilities that the current package does not cover.
Can I buy additional work time?
Yes. Additional administration is PLN 300 net per hour, after separately agreeing the task and budget. Exceeding the allowance does not trigger an automatic extra charge.
Development work is quoted after assessing the scope. Ongoing needs can be included in the subscription.
Can you take over our existing database?
Yes, after reviewing configuration, data and application dependencies. We can take over care at your current provider or plan a migration.
Before launch, we confirm access, provider responsibilities and the ability to recover data.