"Billing".
The account's facts, read-only, inside the site: "Plan & subscription", "Invoices & payment method", "Custom domains" with each certificate's state, and "Account profile", each with "Open ↗", and "Open account console →" for any change.
RUN · ACCOUNT, TEAM AND DOMAINS
The account behind every site.
account.amadalis.ai holds your sites, your domains, your team, your copilot's AI settings, your security policy and your Security log. Each site keeps its own database, its own team and its own admin.
Every figure on this page is as of October 2026.
What it does
Your account lives at its own address, account.amadalis.ai, apart from every site it holds. It has seven tabs, and an agency's account has an eighth, "Clients". Team and Security show only to the account's owner and its Admins.
Joining
-
An invitation.
Accounts open through the Lighthouse program. An invitation names your email address, works once, and expires after the number of days we set, from 1 to 90.
-
"Create your site".
Your organization, the site's name, your name and email address, and a password of at least 12 characters. You can name an existing WordPress site for us to look at; nothing imports until you authorize it.
-
Your email, proved.
A single-use link, valid for 24 hours, verifies the address.
-
Your site, built.
A paid plan goes through Stripe's checkout: "Payment is taken securely by Stripe. We never see or hold your card." The site's own database is then created, prepared and filled with its starting content, and an email says your plan is active. On our own production walk of 27 October 2026, a new site read "Ready" 48 seconds after its checkout.
Sites
Every site you can reach, and the state each one is in.
- "Find a site", then one card for each: its address, its state ("Building", "Ready", "Live", "Down", "Suspended" and others), and its health from our hourly check.
- "Open admin →" takes you into the site's admin at your own role, through a signed pass that lasts 120 seconds.
- "Rename", and "Create a site", which tells you how many sites your plan includes. Every site you add is its own tenant, with its own database, team, domains and copilot.
- Rooms you switch on and off. Each room of a site's admin reads "On", "Off" or "Not in plan", and "Turn off" asks you to confirm. Two switches decide each feature: what your plan includes and what you choose for the site. Both must be on, and a change reaches the site within a minute. Coming soon.
- "Set a schedule" for the site's data exports. Scheduled exports are available on request.
- A site's staging copy is made from a backup, and a card promotes it. Coming soon.
Overview
Your plan, your billing, and where your data lives.
- Your plan and the state of your subscription, and "Move to a paid plan".
- "Manage billing" opens Stripe's own portal, for your card, your invoices, a change of plan, or cancelling. To change the email address your invoices go to, write to support@amadalis.ai and we change it for you. Cancelling does not by itself close your site or erase its content; to close the account, ask support.
- Close the account yourself, with a deletion certificate that documents what was destroyed. Coming soon.
- "Where your data lives". The region your site's database runs in, recorded from the hosting provider when the site was created, "not a marketing claim". The same card says plainly that the network that serves your pages, its caches and AI features run worldwide.
Domains
Your own domain, with one record, and your DNS stays yours.
- "Add a domain" asks one question first: "Is this domain serving a site today?"
- A new domain needs one record at your DNS provider: a CNAME to app.amadalis.ai, or an ALIAS or ANAME record at a root domain. Ownership and the certificate are proved over HTTP, and the certificate renews by itself.
- A domain already serving a site keeps serving while TXT records prove the domain and its certificate in advance. Then one CNAME switch moves it, with no downtime.
- The tab shows exactly which records to add and marks each one "Seen" when it is. A domain reads "Pending verification", then "Certificate ready", then "Active".
- "Make primary", "Redirect to another domain", and "Remove", which asks you to confirm.
- We never ask for your DNS password or a token. Your registrar, your DNS and your email stay yours.
- Only the account's owner adds domains.
Team
The right people, at the right role, on the right site.
- "Invite member": an email address, a role, and "What this grants" in plain words. The invitation is emailed, a link to copy is always returned as well, and it works once within seven days.
- The person who receives it sees "Join {site}" with the role and what it means, and one step creates or joins their login.
- "Change role" shows what the person gains and what they lose before you confirm. "Disable", "Enable", "Resend", "Revoke" and "Recovery" sit beside each member, with search and filters. A disabled member loses their account access, and the Team tab says whether their sign-in on the site could be ended too.
- Each plan has a number of seats, and an invitation beyond it is refused.
- One person can belong to several accounts, and the Sites tab then shows which account each site belongs to.
- The owner can transfer ownership to another member, billing authority included. Coming soon.
- Roles live in the account, not in the site: the site admin's own Users screen says "Roles are managed in your Praxis account → Team."
The roles
| Role | What it adds |
|---|---|
| Viewer | "Reads site content; cannot create, edit or publish." Viewer comes only through SCIM |
| Contributor | "Writes drafts that editors review; cannot publish." |
| Author | "Creates and edits their own content; can publish it in the content editor." Authors work in the Composer, where an Editor or an Admin publishes their pages |
| Editor | Everything on the site except visitor data, form submissions, data export, consent, integrations other than Google Analytics, redirects, team and account |
| Admin | All of it, including visitor data, form submissions, exports, consent, integrations, redirects and the team |
| Owner | One per site: everything an Admin holds, plus billing and domains |
In a sentence: "Invite designer@yourcompany.com as an Editor" · "Disable this person's access". Every team change the copilot proposes waits for your approval.
AI
Your copilot's model, and how much of it you have used.
- "Your copilot's AI model" and "In use now".
- "This month: N% of your AI allowance used". Each plan carries a monthly AI allowance. When your account's allowance is used, the copilot pauses for the rest of the month with "I've paused for this month.", and everything it built keeps working.
- Model tiers, "Fast", "Balanced" and "Frontier", where your plan includes the choice.
- "Your provider keys". On request, the copilot uses your own Anthropic or OpenAI key. With your keys on, every call uses them or is refused, never quietly sent on ours.
- Every member can read this tab; the owner and Admins change it.
Security
The rules for every sign-in, set by you.
- "Team session policy". "Require two-factor authentication for every team member", a session lifetime, an idle timeout, and "Allowed network addresses", so your team can only sign in from the networks you list. Praxis refuses to save a list that would lock you out. Changes apply to the account right away and are written to the Security log. People already signed in to a site pick up the address and session limits within about 30 seconds, longer if the site cannot reach the account. Requiring two-factor does not end a site session already opened from the account.
- API tokens on your sites. When your team sets any "Team session policy" rule, tokens follow its network list, and a member's token needs their access to be on. If two-factor is required, a token's holder must have it on for their own sign-in, even for a token made before the rule. The session lifetime and idle timeout do not apply to tokens.
- "Network addresses in your log". Keep "Network only" (203.0.113.x, the default) or the "Full address" beside each entry. Either way, every governed action on this account is recorded.
- "SCIM provisioning". Your identity provider creates and deactivates members by itself, with a token that is shown once and stored only as a hash. Deactivation always disables and never deletes a member or their history, new members join as Viewers, and roles stay managed in your account.
- Your own sign-in. Change your password while signed in, turn on two-factor authentication for yourself, and see the list of your sessions. Coming soon.
- "Support access". "Grant 4-hour read-only access", for a purpose you state, and revoke it whenever you like. Each grant covers one site, and you can see and revoke the live grants on every site of your account while you are an owner or Admin of an active or suspended site in it. The tab says plainly that Amadalis support can reach your site in four ways, and that each one leaves a record in your Security log: a grant you give; read-only reads while a grant is active; break-glass access in an incident, read-only, with a stated reason and marked "BREAK-GLASS"; and an explicit admin override, only after a confirmation and a reason, which is kept beside the entry.
Activity
Every governed action on your account, on a hash-linked record.
- The "Security log" lists each action in plain sentences: when, what, who, and from which network. Actions by our staff read "Praxis staff", or "Praxis staff, with the copilot".
- Each entry is linked by a SHA-256 hash to the previous entry in the platform's audit log. Editing or deleting an earlier entry breaks the chain, and the platform checks the whole log every night.
- "Download CSV" gives you the newest 10,000 rows, and the download itself is logged.
Clients, for agencies
Every client, under your account.
- An agency's account has a "Clients" tab. Each client is its own organization under your account, with its own sites and people; "New client" sets up a client's first site through the same path every customer uses; your team works inside each client's site and account through access that is recorded and can be revoked; and each client's Team tab reads that your agency manages it.
- We bill your agency for every client site, and you bill your clients yourself, at your own prices. No client of yours is billed by us.
In every site's admin
Account & billing, one room in every site.
"Support".
"How to reach us", with our promise in the product's own words, and "Report a problem", which opens an email that already names your site. Its help links lead to our questions and answers and our help articles. Coming soon.
One sign-in.
A site's own admin refuses emailed sign-in links: "Sign-in is managed through your Praxis account." At account.amadalis.ai, an unknown address and a wrong password get the same answer.
How it works
From payment to "Ready"
One step creates your organization, your site and its production environment, with its own database. Verifying your email releases a free site, or a paid one after Stripe's checkout. Activation checks the amount charged against the plan before it releases the build, and our jobs service then creates, prepares and fills the site's own database.
A database for every site
Each site is a separate database, never tables shared with another customer: either its own database on a shared Neon instance, or a Neon project of its own.
Your domain, step by step
-
You add the domain and answer whether it serves a site today.
-
A new domain: one CNAME, and the certificate is proved over HTTP. A live domain: TXT records first, while your current site keeps serving.
-
Each record reads "Seen" as soon as it is found.
-
The certificate is issued and renews by itself, and the domain reads "Active".
"Open admin" mints a signed pass that lasts 120 seconds, at the member's own role. The account's own address answers only a closed list of pages, and our operators' console is never reachable on it.
What keeps it safe
Apart by design.
Every site is its own tenant, with its own database, team, domains and copilot.
Your role, everywhere.
Entering a site from the account carries your own role, on a pass that expires in two minutes.
A policy that cannot lock you out.
The network list refuses to save if it would shut out the person saving it.
Secrets stay in your browser.
Two-factor, SCIM and billing open in your browser, never in the copilot's chat, and SCIM tokens are kept only as a hash.
Every touch on the record.
Our support's four ways in, and every governed action on your account, land in a hash-linked audit trail, and you can download your Security log.
Approval before change.
When the copilot would add a domain, change security or SCIM settings, or grant support access, it stops at an approval card first.
Common questions
Can I run several sites from one account?
Yes. Each site is its own tenant with its own database, team, domains and copilot, and your plan sets how many you can create.
Do I have to move my DNS to you?
No. A domain needs one record at your DNS provider, and your registrar, DNS and email stay yours.
What happens to a domain that already serves a site?
It keeps serving while TXT records prove it and its certificate, and then one CNAME switch moves it with no downtime.
Can our identity provider manage our team?
Yes. Through SCIM, your identity provider creates members and switches them on or off, and roles stay managed in your account.
Who can get into my site?
Your team, each at their own role. Our support team, in the four ways the Security tab describes, each one recorded. Support entries into every site of your account appear in your Security log while you are an owner or Admin of an active or suspended site in the account; otherwise the log shows only the site your account opens with. A fully erased site’s entries no longer appear.
Can I use my own AI provider keys?
Yes, on request. With your keys on, every call uses your key or is refused.
What happens when our AI allowance runs out?
Each plan carries a monthly AI allowance. When your account's allowance is used, the copilot pauses for the rest of the month, and everything it built keeps working.
Where does our data live?
The Overview tab names your database's region, recorded when the site was created, and says plainly what runs worldwide.