Pricing at a glance
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Decision point | What digna states |
|---|---|
How the price is built | Per module: a base fee plus a price per activated table. You pay only for the tables you activate in each module. |
First module | Unlocks the full platform. No separate platform fee. |
Included from day one | digna Scheduler, digna Data Catalog, all integrations and team collaboration. |
Usage charges | None for API calls, inspections, scans or alert volume. Checks can run as often as you want without changing the price. |
Modules on the pricing page | Data Anomalies, Data Analytics, Data Validation, Timeliness and Schema Tracker. Start with one and add more later. |
Licence | A licence file from digna with an expiration date. Release 2026.11 needs a new one. |
What drives the bill
The pricing page writes the bill as modules × tables (per module). A table you watch with two modules is activated in both, so plan the table count for each module separately.
Costs outside the digna price
digna runs only in your own infrastructure, so you also pay for the host it runs on: at least 16 GB RAM and 10 GB of disk, PostgreSQL 12 or higher for its metrics and a web server, or 32 GB RAM and 50 GB of disk if PostgreSQL shares the machine. Connections profiled through the digna Engine need more memory and disk on that host. By default digna calculates its metrics in the source database, so on a warehouse billed by compute those queries add to the warehouse bill.
Our take
digna's model suits teams that want to check often: the price per activated table does not move with check frequency. Size cost on the modules and table count you expect to reach, not only the first module, and add the server and database you run it on.