Registrations arrive in two spikes: when you announce the session and in the sixty minutes before it begins. Both are writes, and the second one leaves no margin.
An announcement, a registration rush, and then a recording that has to keep serving long after anybody was watching live.
Most sign-ups happen in the sixty minutes before a session begins, and there is no opportunity to fix a slow form once that hour has already started.
Recordings are served through the edge with byte-range support, so a back catalogue of hour-long sessions stays a storage question rather than becoming a bandwidth problem.
Third-party player and scheduling scripts load after first paint, so a slow response from somebody else's service does not stop your registration page rendering.
Registration data bypasses the cache entirely and is stored encrypted, because a webinar signup list is a marketing database with names and employers in it.
Reminder and follow-up emails run on a platform scheduler rather than a visitor-triggered cron, so the message due an hour before the session goes out on time.
A webinar site has three moments and they are weeks apart. The work is making sure the second and third are not treated as an afterthought.
The registration form is uncacheable by nature and it takes its heaviest load in the one hour when a failure cannot be recovered from.
These are the settings that differ from a standard WordPress site on the same plan. Each follows from sign-ups concentrating into the hour before a session starts.
| Setting | What we do | Why |
|---|---|---|
| Registration endpoints | Uncached with write capacity sized for the pre-session hour | Most sign-ups land in the sixty minutes before a session, and a form that fails then is a registrant who cannot try again later. |
| Third-party scripts | Loaded after first paint rather than in the document head | A scheduling or player script that is slow to answer should delay a widget, not the page somebody is trying to complete a form on. |
| Replay delivery | Edge-served with byte-range support | A growing library of hour-long recordings is comfortably the largest bandwidth item on a webinar site. |
| Reminder scheduling | Platform scheduler rather than visitor-triggered cron | A reminder due at nine on a Tuesday morning cannot sit waiting for somebody to visit the site before it sends. |
| Registration data | Encrypted at rest and excluded from cache entirely | A signup list carries names, employers and email addresses, which makes it a marketing database rather than a form log. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, forms that hold up in the final hour, and replays served from the edge.