Crowdfunding hosting for the hour the campaign closes.
A campaign takes pledges for thirty days and decides everything in its final hour, when the total is changing constantly and the settlement is about to run.
The number on the page is the pitch.
A progress bar showing yesterday's total does not just look wrong - it removes the reason somebody was about to pledge.
A total that is current, not cached
The raised figure and backer count change by the minute near the end. Those are resolved per request rather than baked into a cached page, because momentum is the argument.
All-or-nothing settlement at the deadline
Pledges are authorised during the campaign and captured only if the goal is met. That settlement is one batch across every backer, run at close.
Everyone arrives in the last hour
Backers who have been watching for a month all pledge in the final sixty minutes. Capacity is planned around the close time rather than the campaign average.
Authorisations that have not expired
A card authorised on day two has to still be chargeable on day thirty. Expiry windows and re-authorisation are handled rather than discovered at settlement.
A pledge record you can prove
If a campaign fails, backers need to see they were not charged. Records are retained and backed up rather than cleaned up with the campaign.
One moment decides thirty days.
Everything about a crowdfunding site is arranged around a single scheduled event where the money either moves for everyone or for nobody.
- Raised total resolved per request
- Settlement run as one batch at close
- Capacity planned for the final hour
- Authorisation expiry handled before settlement
Pledging while the total moves.
The measurement is a pledge completing during the closing rush, on a page whose headline number cannot be cached.
What we change for crowdfunding sites
Two things drive it: a live total that is also the sales pitch, and a settlement that happens once for everybody.
| Setting | What we do | Why |
|---|---|---|
| Progress figures | Resolved per request rather than cached with the page | The raised total is the argument for pledging, so a figure from an hour ago actively removes the momentum somebody was responding to. |
| Settlement | Run as a single batch at the deadline | All-or-nothing funding means every authorisation is captured together or none is, which is a mass payment run rather than a series of checkouts. |
| Authorisation lifetime | Tracked so cards are still chargeable at close | A pledge authorised early in a thirty-day campaign can expire before settlement, and discovering that during the capture run is discovering it too late. |
| Deadline capacity | Reserved for the final hour rather than averaged | Backers watch for weeks and act in the last sixty minutes, so the campaign mean describes a period that no longer matters. |
| Failed campaign records | Retained rather than removed with the campaign | Backers of an unsuccessful campaign need to be able to see they were never charged, which requires the record to outlive the project. |
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.
Can the progress bar be cached?
How does all-or-nothing funding work technically?
What if a backer's card expires before the campaign ends?
Should I size the site for the whole campaign or the last hour?
Get to the deadline intact.
Move the campaign site across - migration is free, pledge records included.