Pricing

Pricing for teams replacing custom backend work

Vault56 pricing is easiest to understand in the context of what it replaces: backend engineering time, infrastructure assembly, and the ongoing cost of maintaining custom platform foundations.

Storage Cost

Pay for stored data

Vault56 pricing starts with what your product stores, whether that is structured application data or S3-compatible file data.

  • S3 file storage: €12 per TB-started
  • Database storage: €12 per GB-month
  • Useful for products with files, records, or both

Reserved Capacity

Optimize for larger workloads

Teams with bigger commitments can plan around reserved capacity and annual commitments instead of only variable monthly usage.

  • 1 TB annual prepay options are available
  • 20+ TB reserved capacity options are available
  • Useful when storage demand is predictable at scale

Infrastructure Economics

Indicative platform storage numbers

These numbers give a practical view of storage and usage economics for teams planning a Vault56-based product.

S3 file storage €12 per TB-started
Database storage €12 per GB-month
Data transfer out €0.09 per GB
API requests €0.000001 per request

Real-World Examples

What this can look like in an actual app

These examples show how Vault56 costs can map to different product sizes, from a small app to large-scale storage-heavy workloads.

Small App Example

€5.30 per month

Web app with roughly 50 MB of API storage and mobile usage around 5,000 monthly users.

  • Includes API storage
  • Includes transfer out
  • Includes API requests

Pure S3 Example

€120 per month

10 TB of file storage using direct S3 access for teams that mainly need durable storage capacity.

  • 10 started TB at the listed storage rate
  • Useful for file-heavy products
  • Clear baseline for storage-only planning

How to think about price

The economic argument is not just raw infrastructure cost. The larger value is that Vault56 can reduce the amount of custom backend work your team has to design, build, test, and maintain before the interface work even begins.

When this tends to make sense

It is strongest when the app has enough complexity that backend work would otherwise turn into a meaningful project of its own: structured data, files, workflows, approvals, operational controls, or repeated product rollouts.