FortressDB is full speed, like a CDN for data

FortressDB is fast

Optimized for speed, FortressDB was built to handle even the largest, most complex data tables, superfast.

You can compare it to how a CDN delivers rich-media content. CDNs enable a speedy transfer of assets for loading web content so online visitors can interact with websites, see images and stream videos immediately.

Essentially, FortressDB plays the same role as a CDN, but instead of serving images or videos, it serves data.

WordPress wp_posts table

FortressDB is more efficient than traditional custom post types (CPTs) or Advanced Custom Fields (ACFs), which is largely due to the WordPress database infrastructure.

Most content within WordPress is stored as posts, including categories, media, pages and, of course, blog posts. This means that WordPress sites have bloated tables with lots of joins, causing the system to cross-reference data within the same table and slowing performance.

In context, many WordPress plugins also use the wp_posts table. Consider WooCommerce, for each product in its catalogue, there are 29 rows of data in wp_posts. This usually won’t pose a problem for small catalogues, but for larger shops, this affects performance and causes the system to slow.

FortressDB data structure

In FortressDB, each new form or data table is stored as a separate entity and the database performs much faster. There are no joins required to retrieve data and it works efficiently and instantly.


WordPress keeps all revisions in the same wp_posts table. This means that every time a post or page is edited, the previous version (revision) is also saved in wp_posts. It’s clear to see how wp_posts can quickly become much larger than it needs to be. By contrast, FortressDB has a mirror table for every form or custom data table. This means the main, “live” tables only contain current data and all revisions are stored in the appropriate mirror table.


Every form or custom table is made up of fields, such as a field in a contact form asking for your name or email address. If there is one field that is used often for searches, it is possible to add an index to it. The FortressDB plugin has an option to add an index to any field. This works at the database level and speeds up searches.

Field level data encryption

FortressDB is designed with security and privacy in mind. Server level encryption is clearly the most secure option, but if some fields are not sensitive, you may not need to encrypt them. As a guide, personal data like names, emails or phone numbers should be encrypted, but other fields may not need to be. We offer field-level data encryption, enabling you to encrypt personal information only and optimize your data tables for speed.

Google servers

We’ve built our technology stack on the Google Cloud Platform. There are other great choices of cloud services, such as AWS or Azure, but our architects prefer the Google solution. The advantage of using this infrastructure is that it brings great reliability, speed and security. We use Kubernetes, clusters and dockers to provide a scalable solution.

Developer API

FortressDB isn’t just useful for forms, but all custom WordPress development. We want developers to use our API to build awesome features for their websites. To enable this, we’ve created an API test tool for both our REST and sockets APIs. The tool shows you how to call the various methods and endpoints, so you can try it live on your WordPress website.

Read More: Help Docs for API Tool / API Documentation Site