Billing and Usage
All Paradym's billing aligns with one simple principle. We bet on your success. What does this mean? It means that building is focused on helping you grow your solution, and being there every step of the way.
With the addition of the API we’re adjusting our billing to incorporate pay-by-usage. Paradym builders pay a flat fee to access the pro tier, which enables them to deploy to production. Within the pro tier, they then pay for actual transactions used.
Free Tier
The free tier contains 100 transactions a month. Some transactions are always free, check out the overview below to see which ones. Contact us about our extended free tier if you are a student or participating in a hackathon at ana@paradym.id.
The free tier contains:
- 100 transactions a month
- Issuance and verification of AnonCreds over DIDComm
- Issuance and verification of SD-JWT over OpenID4VC
- Testnet only
- Support via the Community Slack (opens in a new tab)
Pro Tier
The pro tier includes 500 transactions for a flat rate of €25 a month; after that, you pay 0.04 per transaction. Some transactions are always free, check out the overview below to see which ones.
The pro tier contains:
- 500 transactions a month
- Issuance and verification of AnonCreds over DIDComm
- Issuance and verification of SD-JWT over OpenID4VC
- Testnet and Mainnet
- Create multiple projects
- Technical via a private slack channel within the Community Slack (opens in a new tab)
Transactions
The below table lists the transaction count for actions performed within Paradym. Each tier defines how many transactions are included, and costs for additional transactions. For all requests, see the API reference (opens in a new tab).
| Transaction | Transaction Count | Comment |
|---|---|---|
| GET requests | 0 | GET requests are free |
| Issue credential | 1 | Each issued credential is counted as a transaction. So an OpenID4VC offer that issues four credentials will be counted as four transactions. |
| Batch credential revocation | 1 | Each successful call to the batch revocation endpoint counts as one transaction. So one call to the batch revocation endpoint revoking 25 credentials, is only counted as one transaction. But 25 calls to the revocation endpoint each revoking one credential, is counted as 25 transactions. |
| Verification | 1 | Each finished verification is counted as one transaction, independent of the amount of credentials in the verification, or whether the verification succeeds or fails. A verification is only counted once it reaches a verified or failed state, so unanswered verifications are not counted as a transaction. |
| Create or update SD-JWT VC credential template | 1 | |
| Create or update Anoncreds credential template | 1-2 | One transaction for creation of the definition, and optionally a second transaction if a schema also has to be created. |
| Create or update presentation template | 1 | |
| Send DIDComm basic message | 1 | Receiving DIDComm basic messages is free |
| Send DIDComm custom message | 1 | Receiving DIDComm custom messages is free |
| Create DIDComm connection | 1 | Creating invitations or reusing an existing connection is free. |
| Workflow Action Execution | 0+ | Each executed action is counted as one transaction |