Mechanics
What happens between clicking Deploy and having a platform, and what happens for the rest of the time you own it. No step here is performed by a person unless it says so.
You choose the subdomain your platform will answer on, and a site name. The subdomain is checked for availability as you type — against every existing site, against a reserved list, and against a short-lived hold placed on names that are mid-checkout, so two people cannot buy the same name at once. Names are lowercase letters, digits and hyphens, and must start and end with a letter or digit.
The email address and password you enter here become the superadmin account of your new site. Choose them as carefully as you would any other administrator credential — this account can reach every screen in your panel, including the money screens. You also give an account email for your customer panel with us; if you do not already have an account, one is created at checkout.
We create a $999 invoice and send you to NOWPayments' hosted checkout, where you pick a coin and pay. The price is fixed in USD when the invoice is created. When you come back, you land on a status page that polls your order until it is done.
Only a fully finished payment activates anything. A payment that under-pays is held for review rather than partly activating your site, and you will hear from us. An invoice that goes unpaid expires after 24 hours and you can simply start again — your subdomain hold expires with it.
Payment settling is the trigger. Nobody clicks anything on our side. Each step below is idempotent and written to a progress log, which is what the status page is reading while you watch it.
If a step fails, the order is marked failed with the reason, you see a message rather than a broken site, and the run can be retried. Retrying re-uses what already exists instead of creating a second copy, and a retry never extends or shortens your paid-through date.
Provisioning starts as soon as your payment settles and runs unattended; the status page polls it every few seconds and tells you the moment your site answers. We are not going to print a number of minutes here — crypto confirmation time is not ours to promise, and we would rather under-claim than publish a figure we cannot stand behind.
Realistic order of operations once the site is answering.
Your site reads its payment credentials from environment secrets on your deployment. There is no screen in the customer panel today where you paste your NOWPayments keys, and we are not going to describe one that does not exist. Until your keys are in place, the deposit endpoint answers "payment system not configured" and your members cannot make a crypto deposit. The same applies to automated identity verification, captcha, analytics and Google sign-in.
Everything else works from the first minute: accounts, plans, wallets, manual USDT deposits you verify yourself, vouchers, commissions, distribution and the whole admin panel.
| When | What happens |
|---|---|
| 1st of the month | The $99 invoice for that month is issued and emailed to you. It also appears in the Billing panel of your customer panel. |
| 7, 3 and 1 days before month end | A reminder email, if the invoice is still unpaid. |
| Whenever you pay | You open the Billing panel, press Pay renewal, and are sent to a NOWPayments hosted checkout for that invoice. |
| When the payment settles | Your paid-through date moves forward one calendar month. If you were overdue or suspended, that state is lifted at the same moment — not at the next daily run. |
| Last day of the month, 23:59:59 UTC | The due moment. From here the lifecycle on the pricing page begins counting. |
Because crypto cannot be auto-debited, there is no stored payment method and nothing that can charge you without you acting. That is a deliberate trade: you will never get a surprise charge, and in exchange you have to remember to pay — which is what the reminder emails are for.
Nothing changes for your members. Your site serves, your automation runs, your admin panel works. Your customer panel shows a banner with the outstanding amount, and we email you at 3 days late and again at 30 days late. If a second month's invoice is issued while you are here, both are listed as arrears.
Your public site is gated behind a renewal-required page. That gate is enforced by your own worker on every request, so there is no way around it — but it is only a gate. Your database, your storage, your members' balances and your customer panel are all untouched. Paying every outstanding monthly invoice lifts the suspension the moment the payment settles.
A suspension is never lifted by hand without the paid-through date moving with it. That rule exists because the alternative — a site flipped back to active while its billing anchor stays in the past — simply gets suspended again by the next daily run, which would be a worse experience than the suspension.
From 91 days past due, the site is cancelled. It serves an "access ended" page, your site's own admin panel closes, and your customer panel shows one thing: the reactivation offer. The outstanding monthly invoices are voided at that point — they are superseded rather than left to accumulate, so you never face a bill for months in which you had no service.
$999 — the same as activation, because it does the same job. There is no back-payment for the months you were cancelled.
The same site, with the same database, the same storage, the same members and the same settings. Your paid-through date is set to the end of the month you reactivate in, and the monthly cycle restarts from there.
Reactivation is available until 180 days past your due date. After that, a daily job permanently destroys your database, storage, session store, both workers and the subdomain, writing a deletion record first. This is irreversible, and it is the only irreversible thing in the whole lifecycle. We email a warning at 150 days and again at 173 days, and a notice after it is done.
Your subdomain is included and always works. If you would rather run on a domain you own, this is the process — and one step of it is a person, not a script.
The Custom Domain panel of your site's detail page takes the domain you want to use and records the request.
The panel shows you the exact DNS record to create at your registrar or DNS provider. Nothing proceeds until that record is in place — we cannot serve a domain that does not point at us.
Activation is a manual step performed by our team. It is deliberately manual rather than automated, and it is the reason we do not quote a turnaround time for it here. Your subdomain keeps working throughout, so your site is never offline while a domain is being attached.