Registry Control Center
Keep the program moving.
Review Charter activity, approve qualified requests, and monitor continuity from one place.
Checking administrator access…
Administrator access
Sign in to continue.
Use the Famitek account authorized for Registry operations.
Action queue
Pending approvals
Everything waiting on you in one place: the first three of each kind of work, then the launched sites, those not selling first. See all opens a queue with its search and pages.
These Charters added no credits after three warnings, and their wallet still cannot pay for the work it refused. Nothing reaches their customers until you approve. Approving takes two steps and cannot be undone; Not now waits a number of days you choose, with a note. A Charter that gives notice is taken over at once and is listed below for information only.
Inspect the exact Charter-submitted revision before deciding. Approval records a content decision; public launch still requires separate domain proof and authorization.
Customer refunds that Stripe could not complete. Settle each one with the customer, then record how it was settled.
Customer work an application could not finish on its own, such as a paid report waiting on an AI provider. An issue closes by itself once its application reports it resolved or the checker, which asks the application every five minutes, finds it resolved. You can also close one with a note.
Authorize an AeoState Charter's launch once its brand is approved, its domain is verified and its customer sign-in is ready. AeoState checks the domain, its certificate and customer sign-in again before the site goes live. Then open customer sales under Launched Charter sites.
AirCM re-checks every Charter's published pages. When a check finds something it cannot decide alone, such as another brand's name or familiar wording, a person at Famitek decides here. Open the site, look at it, then approve it or reject it, always with a reason. A Charter never decides its own.
Opening sales lets customers subscribe to this Charter's offers on its own site. Open sales once the application has shown it can deliver to a paying customer.
Wallets
Charters and credits
One wallet per Charter pays for all its applications. Runway is how long its credits last at the pace of the last 30 days. Open a Charter for its top-ups, usage, customers and warning thresholds.
| Charter | Available | Plan / bought | Runway | Applications | Customers | Status |
|---|
Before a takeover
Warning rules
When a Charter's available credits fall below its application's threshold, the application sends warning 1, then warnings 2 and 3 two days apart, while work still runs. Credits back at the threshold end the warnings. A takeover still needs work the wallet refused: at the earliest two days after warning 3 and two days after that refusal. A threshold set for one Charter, in its panel, replaces the default.
Platform AI
Application keys
The key an application uses for every Charter that chose the application's own AI key. It is encrypted before it is stored, sent sealed so only the application can open it, and never shown again, to administrators, Charters or their customers.
Customer protection
Cancellation and continuity
Decision history
Charter journeys
Read-only. A decision is final for its revision; the Charter submits a new revision to change it.