Billing Policy
Effective date pending publicationVersion 1.0
This policy explains what happens to your account when a payment fails or your credit balance runs out. It forms part of the Customer Terms of Service.
We publish it because being suspended without warning is the worst thing a platform can do to someone running a client's site. Nothing here happens without us telling you first, and paying restores service immediately at any stage.
#1. Credits
Your plan includes a monthly allocation of credits. A credit is a unit of compute — the pricing page explains what one buys.
Credits are spent on executions. An execution is a workflow run or a direct call to an API template, however it was started — a visitor loading a page, an API request, a scheduled job, you testing something in the editor, or your AI assistant calling it over our MCP interface. The trigger makes no difference; what costs is the work done.
Reading and editing your workspace is free. Browsing your content, changing a datafile, authoring a workflow, and saving a draft cost nothing — whether you do it yourself or an assistant does it for you. Only executions are billed.
- On a paid plan, an unused allocation rolls over once — it stays usable through the following month, then expires.
- On the free tier, the allocation resets each month and does not roll over.
- Credits you buy never expire. They stay on your account until you use them, and a change of plan does not touch them.
- Changing plan clears your included allocation, including anything rolled over, whether you upgrade or downgrade. Only the credits you paid for separately survive.
- Credits have no cash value and are not refundable or exchangeable for money.
- If you cancel, credits stay usable until the end of the period you have paid for.
We do not automatically charge you for more credits. When your balance runs low we tell you, and you decide whether to top up or upgrade. You will never receive a bill for usage you did not agree to in advance.
#2. When your credits run low
We warn you as the balance falls, and the warnings get louder rather than merely more frequent. Every one of them carries a one-click link to top up or upgrade:
| Balance | What we do |
|---|---|
| 50% remaining | Notice in the dashboard |
| 20% remaining | Email to the account owner |
| 10% remaining | Email, plus a banner in the dashboard you cannot miss |
| Exhausted | Email, and the dashboard tells you exactly what has stopped — see Section 3 |
#3. When your credits are exhausted
Executions stop. Pages, API routes, scheduled jobs, editor test runs, and anything your assistant calls over MCP are all executions drawing on the same balance — so when it reaches zero they stop together. There are no stages, because there is nothing left to spend.
Reading and editing keep working. You can still open your workspace, change your content, and fix whatever caused the spike; you just cannot run anything until you top up.
You are not billed for going over. Metering has a small lag and a run in progress is not interrupted, so your balance may dip slightly below zero. We absorb that. It is not carried forward, and it is not deducted from your next top-up.
What keeps serving. Two things are unaffected, because neither runs a workflow:
- Cached pages, until their cache expires
- Published datafiles and media assets, which are static files and serve regardless
How long cached pages last is set by you. A page with a one-hour cache setting keeps serving for about an hour; a page with caching turned off — the default — stops immediately. If you want a site that rides out an interruption, set a cache TTL on pages that can tolerate slightly stale content, and load anything volatile from a published datafile the page fetches directly.
Topping up or upgrading restores everything immediately. Nothing is deleted, nothing is suspended, and you owe us nothing — running out of credits is not a payment problem.
#4. When a payment fails
This one is staged, and it is worth saying why the difference is deliberate. When your credits run out there is nothing left to spend, so everything stops together. When a payment fails you still have credits — you are a customer with a card problem — so we choose what to keep running for you, and we take the least visible things away first.
| Days | Stage | What happens |
|---|---|---|
| 0 | Grace begins | Scheduled jobs pause. Everything else works normally. We email you. |
| 1–7 | Grace | Sites serve normally. Warnings escalate. |
| 8–14 | Degraded | Pages and API routes stop running. Cached pages serve until their cache expires. Dashboard warnings are prominent. |
| 14 | Suspended | Endpoints stop serving. Visitors see a plain holding page. |
| 14–90 | Dormant | Your hostnames stay reserved and your content is retained. |
| 90 | Deleted | Your content is deleted, after a final warning. |
The holding page does not mention billing. The person visiting a site is usually not the person who owes us money.
Paying at any stage restores service immediately. There is no penalty, no reactivation fee, and no need to start a new subscription.
#5. Hostnames
While your account is dormant we hold your hostnames rather than releasing them, so they are waiting for you if you come back.
One exception, in Customer Terms §7: if your account is dormant or overdue and someone demonstrates control of the DNS for a hostname pointed at us, we may release that hostname so they can point it elsewhere. We will email you first and give you a chance to respond.
Releasing a hostname removes the connection to your workspace and nothing else. Your content is not transferred, shared, or made available to anyone.
#6. Free accounts
Running out of credits. When a free account's credits are exhausted, executions stop, exactly as on a paid plan. Cached pages serve until their cache expires, and published datafiles and media keep serving.
You can top up or upgrade. Buying credits restores executions; upgrading raises your other limits as well.
Credits only lift the credit limit. Storage, datafiles, and domains are set by your plan, and a top-up does not change them.
Inactivity. Free accounts have no payment clock, but storage is not free for us to keep.
If a free account is inactive for 90 days, we will email you, then archive its media, and eventually delete the account.
Inactive means all of the following, for 90 days straight:
- none of your endpoints received a request at our servers (requests answered entirely from cache do not reach us, so they do not count)
- no workflow or schedule ran
- nobody signed in to the account
- nothing reached it through our API or MCP server
An agent counts. If you drive your workspace with an AI assistant rather than by signing in, that activity keeps the account alive on its own — you do not have to log in to prove you are still there.
Any one of those resets the clock. A site nobody visits and a tool nobody opens go quiet; a tool you use every day never comes close, even if you never change it again. We are reclaiming storage from accounts nobody is using — not from accounts nobody is editing.
#7. Refunds
Fees are not refundable. If you cancel, your plan runs to the end of the month you have paid for and is not renewed, and your account moves to the free tier.
The exceptions are set out in Customer Terms §9.
#8. If something goes wrong
If you have been suspended and believe it is a mistake — a payment that actually went through, a card that would have succeeded on retry — email support@tessryx.com and we will sort it out. Tell us before you rebuild somewhere else.
#9. Changes
We may update this policy by posting a revised version. If a change reduces the notice you get or shortens a period in your favour, we will tell you at least 30 days in advance.
Tessryx LLC, 8605 Santa Monica Blvd #347695, West Hollywood, CA 90069