MirCrypt — Product · Annual managed service

MirCrypt

Post-quantum encryption for PostgreSQL, with dedicated annual support

A database is not safe forever: data encrypted today with classical algorithms (RSA, ECC) could be decrypted by tomorrow's quantum computers — this is the "Harvest Now, Decrypt Later" risk. MirCrypt is Miriade's annual support for pg_vault_tde, the PostgreSQL extension that encrypts data with keys designed to withstand quantum attacks. We guide you through installation, secure key management, and long-term maintenance — with the key always and exclusively in your hands.

At a glance

The product in a nutshell

What it is
Miriade's annual support for pg_vault_tde, the PostgreSQL extension that encrypts data with keys resistant to quantum computers.
Type
Product / managed service — annual coverage for a single database.
Tiers
Two: Base and Advanced.
When you need it
Confidential, long-lived data on PostgreSQL, or a need to get ahead of the post-quantum transition.
Scope
Post-quantum encryption, keystore, key management, table- or column-level granularity.
Data sovereignty
The key always remains exclusively the customer's: Miriade neither stores nor accesses it.
What it solves

Protecting data against the quantum future, too

Many organizations keep data on PostgreSQL that must remain confidential for years or decades — healthcare, financial, industrial, and public-sector data. MirCrypt addresses the concrete risks of this scenario.

"Harvest Now, Decrypt Later": data encrypted today with classical algorithms, intercepted, and decrypted tomorrow by quantum computers.
Non-granular encryption: encrypting the whole database is costly; MirCrypt encrypts individual tables (or columns) based on their actual criticality.
Keys and sovereignty: entrusting the key to third parties creates risk; here it stays with the customer alone, on Vault, OpenBao, a local keystore, or an HSM.
Error-prone installation: a misconfigured extension can lose the key or degrade performance.
Long-term maintenance: it is not "install and forget"; it needs updates, bug support, and evolution over the years.
No in-house expertise: managing keystores, key rotation, and updates requires dedicated skills.
What it includes

From design to continuity

Assessment & design

Analysis of the PostgreSQL environment and architectural design of the pg_vault_tde installation, identifying critical tables and columns.

Installation & configuration

Installation and configuration of the extension and related architecture (e.g., keystore), validated by Miriade.

Key provisioning & management

Generation and secure management of the encryption key, owned exclusively by the customer. No key is stored by Miriade.

Selective activation

Encryption enabled at the level of a single table or, in the Advanced tier, a single column, based on actual criticality.

Support & updates

Direct bug support, with extension updates planned and applied by Miriade.

Rotation & customization

Periodic key rotation and customization on request: dedicated keystores, HSMs, custom algorithms or formats.

The two tiers

Base or Advanced

Both are delivered as active annual support on a single database. Protecting multiple databases requires multiple subscriptions, one for each.

Comparison of the two support tiers
Scope MirCryptBase MirCryptAdvanced
Coverage A single database, annual support A single database, annual support
Assessment and design Performed by Miriade Performed by Miriade
Installation Performed and validated by Miriade Performed and validated by Miriade
Supported keystores HashiCorp Vault, OpenBao, local On customer request, including HSM
Encryption granularity Table Table or column
Key management Handled by the customer + Miriade best practices Full governance with Miriade
Key rotation Handled by the customer Full governance with Miriade
Encryption algorithm Standard post-quantum Post-quantum, with a custom fork
Support and bugs 8x5, via ticket 8x5, via priority ticket
Updates Planned and applied by Miriade Planned and applied by Miriade
Long-term support Included in the annual renewal Maintenance even beyond 5 years
Best suited for Technical teams that want to adopt encryption safely Enterprise contexts or highly critical data
How it works

The path, step by step

1

Assessment and architectural design

Analysis of the PostgreSQL environment (on-premises, cloud, or hybrid), identification of critical tables and columns, performance testing, and definition of the most secure configuration.

2

Installation

Installation of the extension and supporting components (e.g., keystore), with correct key storage.

3

Key provisioning

Generation of the encryption key, owned exclusively by the customer. No key is stored by Miriade.

4

Selective activation

Encryption enabled at the level of a single table (Base) or a single column (Advanced), according to actual protection needs.

5

Transparent operation

Encrypted data is transparently readable and writable by whoever holds the key, and unreadable to anyone else, including the system administrator.

6

Support, rotation, and long-term support

Direct bug support, periodic key rotation, and updates to the extension over time; in the Advanced tier, maintenance even beyond 5 years.

The non-negotiable

The key, always in your hands

The encryption key remains always and exclusively the customer's: Miriade neither stores nor accesses it.

The extension is developed in-house by Miriade and released to the open source community: no lock-in, no dependence on closed proprietary solutions. The cryptographic scope and the level of control over the key (up to a dedicated fork with HSM) are defined together with your security team during the assessment.

Related

In the context of data security

Not on PostgreSQL yet? With DBPorter, Miriade automatically converts your database's structure and code to PostgreSQL, as a first step toward adopting MirCrypt.

FAQ

Frequently asked questions

Do I have to choose the Advanced tier to protect sensitive data?

No. The Base tier already covers table-level encryption with a standard keystore. The Advanced tier is for column-level granularity, a dedicated fork, or custom configurations.

Can I protect multiple databases with a single subscription?

No: each subscription (Base or Advanced) covers a single database for one year. Multiple databases require multiple subscriptions.

Who owns the encryption key?

Always and exclusively the customer. Miriade never stores or accesses it.

Can I move from Base to Advanced later?

Yes, at annual renewal or, in some cases, during the subscription, subject to a technical assessment.

What if I'm not on PostgreSQL yet?

Miriade provides DBPorter to automatically migrate your database's structure and code to PostgreSQL, as a first step toward MirCrypt.

What does "post-quantum" mean?

The keys are designed to withstand attacks from future quantum computers, anticipating the standards defined by NIST and protecting long-lived data.

Want to protect your PostgreSQL data with post-quantum encryption?

Let's assess together which MirCrypt tier best fits your database and your security requirements.

Request a MirCrypt assessment

Encrypt your data quantum-proof

Tell us which critical data you keep on PostgreSQL and your security requirements: together we'll assess which MirCrypt tier best fits your database.

Post-quantum encryption at table or column level.
The key always and only yours: Vault, OpenBao, local or HSM.
Annual support: installation, updates, rotation.

We use the data you submit only to get back to you about this request.