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.

Current package prices and add-on costs

Loading current prices.

Loading

Fetching package pricing

This section is populated from the public package pricing API and cached briefly in the browser.

Feature-Priced Extras

Standalone feature pricing not bundled into a package

These cards come from the public feature pricing API and only show features with a non-zero published base cost.

Loading

Fetching feature pricing

Standalone feature prices are loaded in real time and updated automatically when the API changes.

Default Usage Rates

Live public rates for storage, transfer, and requests

These figures come from the public pricing API. Package cards above can override these rates when package pricing is published.

S3 file storage €12 per TB-started
Database storage €12 per GB-month
Data transfer in €0 per GB
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.