IMPORTANT! Sign-ups after July 2023 are using a new back-end architecture, and there are no transaction usage limits applied to those. If you notice degraded performance related to usage, please contact us to discuss upgrading your service.

For the legacy hosted (cloud) version of Staff.Wiki, we enforce limits on the number of transactions that can be posted through the system each month. If an account exceeds the service tier limit, then we will notify you to discuss upgrading to the next service tier (eg. tier 2 is double the base service charge) or alternative hosting arrangements, such as on your own server. We do this to maintain a consistent experience on our multi-tenant server infrastructure for all users.

Note: This is enforced passively and we will always give you adequate notice before any changes are made.

Service tiers:

• Tier 1 (default cloud service): 0 to 1,000 total transactions per month.
• Tier 2 (upgraded service tier, may result in back-end relocation): 1,001 to 3,000 total transactions per month. Having more than 50 users may also qualify for Tier 2.
• Tier 3 (will usually require dedicated server): 3,001 and higher.

The number of transactions are derived from:

• Any form submission over the period of that month, including draft policy saves (each is 1 transaction)
• Viewing pages (10 page loads = 1 transaction)
• Database size (2 transactions added for each MB)
• Total storage of uploaded attachments (2 transactions added for each MB uploaded)

You can monitor your own transaction count by going to Admin Tools / Functions / Usage Stats. Note: You will need to be an administrator to run this command.

Please note: If you are using the on-premise (or self-hosted) edition, there are no transaction limits. These limits only apply for our cloud service editions where it is hosted by us or our partners.