Gravity Forms hosting for sites where the form is the product.
A form-driven site accumulates its problems quietly. Entries pile up, uploads pile up, and the admin screen you use to read them gets slower every month.
What a busy form leaves behind.
Nothing here is about rendering a form. It is about the year of data that arrives through it.
An entries table that stays fast
Every submission is rows in the entry and meta tables, and the admin list view queries across all of them. Those lookups are indexed so reading last week's entries does not get slower every month.
Uploaded files are not public
Attachments submitted through a form are stored behind access checks rather than in a browsable uploads path, because people submit passports and invoices through forms without thinking about it.
Notifications that finish sending
A submission can trigger several notifications and a handful of webhooks. Those run with limits that let the chain complete rather than timing out after the first two.
Spam absorbed before it costs anything
Public forms attract automated submissions constantly. That write volume is absorbed by your plan's limits rather than filling the entries table faster than anyone can moderate it.
Entries in the backup
Submissions are business records, often the only copy. They are in the daily backup along with the uploads attached to them.
The admin screen nobody optimises.
Form plugins are judged on the front end and lived with on the back end. The entry list is where a form-heavy site actually becomes unpleasant to use.
- Entry list stays fast as submissions accumulate
- Attachments behind access checks
- Notification chains given room to finish
- Exports that do not time out
Reading entries should stay instant.
The number that matters is how long the entry list takes to load in year two, not how fast the form renders on day one.
What we change for Gravity Forms
A form plugin's cost is not the form. It is the table behind it, which grows every day and is never cleaned up.
| Setting | What we do | Why |
|---|---|---|
| Entry table indexing | Indexed on form, date and status | The admin entry list filters on exactly those three, and unindexed it scans a table that grows with every submission. |
| Form attachments | Stored behind access checks | People submit identity documents and invoices through forms, and a guessable uploads URL exposes them to anyone. |
| Notification chains | Given execution room beyond a normal request | One submission can fire several emails and webhooks in sequence, and a default timeout truncates the chain silently. |
| Export runs | Own memory and execution ceilings | Exporting a quarter of submissions is a batch job that a page request's limits would kill part way through. |
| Spam volume | Absorbed within plan limits rather than blocking writes | Public forms receive automated submissions continuously, and that write load is constant rather than occasional. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why does my entry list get slower over time?
Where do form file uploads go?
Can I export a large number of entries?
Does this apply to WPForms and Formidable too?
Keep the data usable, not just collected.
Move the site across. Migration is free, entries and attachments included.