MinervaDB Partner Network · Database partner program for Systems Integrators, ISVs and SaaS, Distributors and Resellers
MinervaDB Partner Network: the Database Partner Program
Sell the database expertise your customers keep asking for. The MinervaDB database partner program puts a senior-only, vendor-neutral database engineering bench behind your business: consulting, 24×7 consultative support, remote DBA and managed services across 13+ engines and every major cloud DBaaS, delivered under your customer relationship, with recurring economics that renew year after year. It is built for Systems Integrators, ISVs and SaaS companies, Value-Added Distributors and Value-Added Resellers that need a database tier they can put their name behind.
01 · Why partner
Why partners bring their database workstreams to the MinervaDB database partner program
Database workstreams stall or kill larger programmes. A performance crisis surfaces mid-migration, an Oracle exit stalls on PL/SQL conversion, an HA redesign fails its first failover drill, a warehouse bill blows past forecast. These are the moments where a programme either gets a credible answer or loses the quarter.
Win deals you currently walk past
MinervaDB principals scope, de-risk and deliver the database tier while you own the programme, the customer and the commercial relationship. The database workstream becomes a reason to win the deal rather than a reason to qualify out, and the RFP's database sections get answered by people who have done the work.
Earn recurring, not one-off
Partners earn on annual subscriptions, 24×7 consultative support, remote DBA and managed services, that renew above 90% year over year. A subscription sold in year one is still paying in year three, and each renewal is an opportunity to attach engines, environments or coverage tiers. Project work is the entry point; the subscription is the business.
Keep the account, guaranteed by contract
Account protection is written into the database partner program agreement, not left to goodwill: no cross-selling into partner-registered accounts without written consent, no subcontracting of the partner's brand or relationship to a third party, mutual non-solicitation of personnel. Deal registration is honoured for the full protection window of your tier, and disputes are resolved on the registration record.
02 · Operating model
Database partner program operating model: one senior bench, four commercial models
The database partner program runs on four tracks around a single delivery organisation. Each track maps to a distinct commercial model and a distinct set of technical deliverables, and all four draw on the same named senior engineers.
Figure 1. The database partner program operating model: what the partner owns, what MinervaDB owns, and the four tracks between them.
The bench behind the database partner program is the same one that serves MinervaDB's direct enterprise clients: principal-level engineers across PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, Db2, MongoDB, Cassandra, Redis and Valkey, ClickHouse through the sister practice ChistaDATA, SAP HANA, the warehouses and every major cloud DBaaS. There is no L1 ticket wall between your customer and the person who will fix the problem, and there is no partner-side delivery subcontracting, which is precisely why customers renew.
What the partner keeps is everything commercial: the programme, the customer, the contract, the invoice and the relationship. What MinervaDB keeps is everything technical: the scoping, the evidence, the delivery, the rollback and the renewal. The database partner program agreement draws that line explicitly so that neither side has to negotiate it deal by deal.
03 · Delivery standard
The delivery standard your customers get through the database partner program
Every engagement sold through the programme, audit, incident, migration or steady-state operations, is delivered to the same method: named senior engineers, evidence cited to the engine's own telemetry, findings prioritised with escalation flags, and a rollback path before anyone touches a running system.
Figure 2. The database partner program delivery standard: the five-stage engagement method and the telemetry each finding is cited to, by engine.
Findings under the database partner program are evidence-first. On PostgreSQL that means pg_stat_statements, wait attribution from pg_stat_activity and auto_explain output; on MySQL and MariaDB, performance_schema and the sys schema; on SQL Server, Query Store and the wait-statistics DMVs; on Oracle, AWR and ASH; on MongoDB, the profiler and explain("executionStats"); on Cassandra, nodetool histograms and repair history; on Redis and Valkey, INFO, SLOWLOG and the latency monitor; on ClickHouse, system.query_log, system.parts and system.merges. Each finding follows observation, interpretation, recommendation, is prioritised P0, P1 or P2, and carries an ESCALATE flag where a risk requires a decision above the engineering level.
Audits run against read-only telemetry with monitoring-grade access: no write access, no application data. Your customer's security team can approve the access model in one review, and findings arrive within 48 to 72 hours of telemetry collection. Every recommendation carries impact, risk and a rollback path, with a verification query before and a validation query after any change, and a confirmation gate written into the procedure for anything destructive. The method is the one described on the full-stack database optimization page; partners sell the same discipline MinervaDB applies to its own accounts.
04 · Four tracks
The four database partner program tracks
Resale margins and referral fees escalate by tier and are disclosed in the Partner Program Guide on application. Each track below lists the commercial model and the technical deliverables it carries.
Systems Integrators: Services Alliance
The database partner program track for programme owners: an embedded database workstream inside your programmes, contracted as a subcontract or a tri-party agreement. The migration factory covers heterogeneous migrations with schema and PL/SQL conversion, CDC and replication-based near-zero-downtime cutovers with Debezium, DMS, GoldenGate or logical replication as the source dictates, and a documented rollback for every cutover window. Architecture validation includes RPO and RTO verified against a rehearsed failover before go-live, not a whiteboard assertion. Joint bid support covers the database sections of RFPs and SOWs. After the programme closes, the environment converts to managed services with partner economics on the subscription for as long as it renews.
ISVs and SaaS: Embedded Backline
A 24×7 backline for the databases inside your product, with pageable escalation SLAs your on-call engineers can rely on at three in the morning: S1 acknowledged in 15 minutes, S2 in 12 hours, S3 in 24 hours, S4 in 48 hours. Performance engineering that protects gross margin: query and schema optimisation, multi-tenant isolation and noisy-neighbour management across shared clusters, and capacity architecture planned ahead of the sales forecast rather than after the outage. A compliance pack, documented operational model and escalation architecture, presentable in your own customers' security reviews. A white-label option is available where the backline must appear under your brand.
Value-Added Distributors: Territory Distribution
The database partner program track for distribution networks: distribution rights for the subscription catalogue in defined territories or verticals, with second-tier reseller recruitment and management run on MinervaDB's framework. A wholesale rate card with volume tiers, a deal-registration hub for your reseller base, territory enablement with localised campaign kits, and quarterly business reviews on pipeline, attach rate and renewal health.
Value-Added Resellers: Resale and Referral
Resell annual subscriptions or refer per deal. The audit-attach motion is the fastest entry: a fixed-scope database audit attached to any infrastructure, cloud or security deal, with findings in 48 to 72 hours, a low-friction way to open a database conversation in an account you already own. Campaign kits cover PostgreSQL upgrade readiness (14 leaves support in November 2026), Oracle estate and licensing review, cloud database cost governance and SQL Server modernisation. Deal-registration protection applies from the first registered opportunity. Where the customer has committed cloud spend, subscriptions can close as AWS Marketplace private offers or Azure Marketplace private offers against that commitment.
05 · Embedded backline
How the database partner program backline for ISVs and SaaS is wired
The backline is an escalation architecture, not a mailbox. Triggers, severities and the boundary between your on-call and MinervaDB's engineers are agreed at onboarding and written into the runbook your platform team already uses.
Figure 3. The database partner program embedded backline: your customers see your brand, your on-call pages the backline on defined triggers, and the work between incidents is where the gross margin is protected.
Between incidents the database partner program backline does the engineering that keeps a multi-tenant platform inside its margin: per-tenant quotas and resource governance, shard and pool design across shared clusters, index and query work driven by the profiler and slow logs, and upgrades and schema migrations rehearsed on a representative copy before they reach the fleet. Capacity is planned from the sales forecast and the measured working set, so the platform is sized before the customers arrive rather than after the first noisy tenant.
For regulated customers the compliance pack documents the operational model, the escalation architecture, the access model and the audit trail in the form a SOC 2, PCI DSS, HIPAA or GDPR reviewer asks for it. Under the white-label option the backline appears under your brand in tickets, status pages and post-incident reports, while the database partner program agreement keeps the account protection and non-solicitation terms in force.
06 · Engagement lifecycle
From audit-attach to renewal: how the database partner program compounds
Most partner accounts follow the same path: a fixed-scope audit opens the conversation, a project fixes what the audit found, and a subscription keeps the estate healthy and the partner paid. The split of responsibilities is the same at every stage.
Figure 4. The engagement lifecycle and the responsibility split that keeps the customer relationship with the partner.
The database partner program audit is deliberately small: read-only access, a representative telemetry window, findings in 48 to 72 hours, ranked by cost, latency and availability effect. It is the lowest-friction way to add a database line to a deal that was about infrastructure, cloud or security, and it produces the evidence the project scope is written from. The project, whether a migration, an HA redesign, a performance remediation or a cost-governance programme, runs under the delivery standard above with a rollback on every cutover.
The subscription is where the economics live. Annual 24×7 consultative support, remote DBA or managed services renew above 90% year over year, the partner's commission line renews with them, and each renewal is the moment to attach the engines, environments or coverage tiers the estate has grown into. MinervaDB's job is to keep the customer renewing; the partner's job is to keep the relationship. Neither side crosses that line.
07 · Tiers
Database partner program tiers: Registered, Select, Premier
Benefits escalate with demonstrated pipeline and delivery collaboration. Tier progression criteria and the commercial schedule are set out in the Partner Program Guide.
Figure 5. The three database partner program tiers, their deal-registration protection windows and the benefits each adds.
| Benefit | Registered | Select | Premier |
|---|---|---|---|
| Deal-registration protection | 90 days | 120 days | 180 days |
| Partner portal and directory listing | Yes | Yes | Yes |
| Campaign kits | Standard | Localised to territory and vertical | Joint campaign planning with shared targets |
| Market development funds | — | Co-branded campaigns and events | Co-branded campaigns, events and co-hosted customer briefings |
| Pre-sales scoping | Standard queue | Priority scheduling | First call on joint bid support for strategic pursuits |
| Reviews | — | Quarterly pipeline reviews | Named partner manager and formal quarterly business reviews |
| New service lines | On general release | On general release | Early access |
08 · Onboarding
How database partner program onboarding works: 30, 60, 90
First registered deal inside 90 days is the plan built together. Onboarding is a 30/60/90 sequence with a named owner on both sides for every milestone.
Figure 6. Database partner program onboarding, onboard, activate, produce: the 90-day path from agreement to the first registered deal.
Days 1–30 · Onboard
Partner agreement executed, portal access provisioned, a sales foundation session for your account teams, brand and campaign kits delivered.
Days 31–60 · Activate
Campaign kit localised to your territory and vertical, a technical overview for your solution engineers covering the audit method and the engagement model, and joint account mapping against your installed base.
Days 61–90 · Produce
First registered opportunity, first co-hosted customer conversation, and a tier-progression plan with the pipeline targets that move you to Select.
09 · Platform coverage
One database partner program agreement, the full engine roster
Partners do not need a separate vendor relationship for each database in a customer estate. One agreement covers every engine below, with the version lines MinervaDB currently supports in production.
| Family | Engines | Current lines supported |
|---|---|---|
| SQL / RDBMS | PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, Oracle Exadata, IBM Db2 (LUW and z/OS) | PostgreSQL 14–18 · MySQL 8.4 and 9.7 LTS · MariaDB 10.11, 11.4, 11.8 and 12.3 LTS · SQL Server 2022 and 2025 · Oracle 19c, 23ai and 26ai · Db2 11.5 and 12.1, Db2 13 for z/OS |
| NoSQL | MongoDB, Apache Cassandra, Redis, Valkey, Milvus | MongoDB 8.0 and 8.3 · Cassandra 5.0 · Redis 8.x · Valkey 9.1 · Milvus 3.0 |
| Distributed SQL | CockroachDB, YugabyteDB, TiDB, Spanner | Current GA lines, with the consistency and topology trade-offs of each documented |
| Analytics and streaming | ClickHouse (delivered through ChistaDATA), SAP HANA, Snowflake, BigQuery, Redshift, Databricks, Trino, Apache Kafka | ClickHouse 26.8 LTS · Kafka 4.3 · Trino 483 · Redshift RA3, RG and Serverless |
| Cloud DBaaS | RDS, Aurora, DynamoDB, ElastiCache, MemoryDB, AlloyDB, Cloud SQL, Azure SQL, Azure Database for PostgreSQL and MySQL, Cosmos DB, MongoDB Atlas, MySQL HeatWave | Managed-versus-self-managed divergence maps maintained for each, joined to billing data in every audit |
Engine-specific service detail behind the database partner program is on the full-stack database optimization page and the database consulting page; the consulting overview lists every engine practice a partner can sell.
10 · Questions
Database partner program: frequently asked questions
The questions partner managers are asked most often on the first call.
Who delivers the work sold through the database partner program?
MinervaDB's own named senior engineers, directly, on every engagement. Partner-side delivery subcontracting is not permitted and MinervaDB does not subcontract the partner's brand or relationship to a third party. That is the reason the subscriptions renew above 90% a year, and the reason the partner's commission line keeps compounding.
How is my account protected?
Account protection is in the database partner program agreement: no cross-selling into partner-registered accounts without written consent, no subcontracting of the partner relationship, mutual non-solicitation of personnel, and deal registration honoured for the full window of your tier, 90, 120 or 180 days. Disputes are resolved on the registration record, not on who spoke to the customer last.
What do partners earn, and on what?
Resale margins and referral fees escalate by tier and are disclosed in the Partner Program Guide on application. They apply to annual subscriptions for 24x7 consultative support, remote DBA and managed services, and to project work sold through the programme. Because subscriptions renew above 90% year over year, a subscription sold in year one is still paying in year three.
Which track should we apply for?
Systems Integrators with programmes that carry a database workstream take the Services Alliance. ISVs and SaaS companies with databases inside their product take the Embedded Backline. Distributors with a reseller base take Territory Distribution. Resellers who want to attach a database line to infrastructure, cloud or security deals take Resale and Referral. A partner manager confirms the track on the application review.
How quickly can we take a first deal to market?
The 30/60/90 onboarding plan targets a first registered deal inside 90 days: agreement and kits in the first 30 days, localised campaign and joint account mapping by day 60, first registered opportunity and first co-hosted customer conversation by day 90. The audit-attach motion is the fastest entry because findings arrive in 48 to 72 hours.
What access does a database audit need from our customer?
Read-only, monitoring-grade access to telemetry: the engine's own statistics views and the cloud provider's metrics. No write access and no application data. The access model is designed so a customer security team can approve it in one review.
Can subscriptions be bought against committed cloud spend?
Yes. Where the customer has committed AWS or Azure spend, subscriptions can close as AWS Marketplace private offers or Azure Marketplace private offers against that commitment, with partner economics preserved.
Does one agreement cover every engine in a customer estate?
Yes. One database partner program agreement covers the full roster: PostgreSQL, MySQL, MariaDB, SQL Server, Oracle and Exadata, Db2, MongoDB, Cassandra, Redis, Valkey, Milvus, the distributed SQL engines, ClickHouse through ChistaDATA, SAP HANA, the warehouses, Kafka, Trino and every major cloud DBaaS. Partners do not need a separate vendor relationship per database.
11 · Apply
Apply to the Partner Network
Complete the database partner program application below. Applications are reviewed by a partner manager within two business days; approved applicants receive the Partner Program Guide, the commercial schedule for their track and a proposed 30/60/90 onboarding plan.
MinervaDB delivers all engagements directly; partner delivery subcontracting is not permitted, which is precisely why your customers renew. Questions before applying can go to the MinervaDB contact desk or +1 (844) 588-7287.
Put a senior database bench behind your business
Four database partner program tracks, three tiers, one delivery standard, and a subscription line that renews above 90% a year. The first registered deal is planned for inside 90 days.