An account that is only yours, on an environment that is only yours
- The account is not yours
- You cannot see what went wrong
- And you cannot fix it yourself
- The account is yours alone
- The environment stays fixed
- Status is visible any time
Where your money goes
Your subscription pays for the third line only. Exact tiers and amounts are shown in the console subscription centre.One environment, running only your account
The subscription is bound to the environment, and the account runs on top of it. What hurts an account most is having its conditions shift around — it gets slower, and eventually stops working. So once assigned, your environment is fixed. When an account has to be replaced, only that layer changes; your environment is untouched.
This environment stays reserved for you and does not change.
What state your environment is in
Once you subscribe, the running state of that environment is visible in the console at any time. Here is a sample
- The details of your environment are visible only to you.
- Check results are shown as measured, with no polish applied.
- Want to confirm the current state? Refresh the check yourself, any time.
Your own machine stays the way you left it
The hosted account runs on your own computer, but it does not disturb the setup you already had: preserved in full before we take over, kept separate while hosting runs, and restored exactly afterwards. None of it needs your hands.
-
Before takeover
A snapshot of your own environment is taken first
- Your existing setup is preserved
- Hosting stays isolated from your own environment
- Your own settings are left untouched
-
While running
Continuously checked — you should not have to notice
- Account availability is checked automatically
- You hear from us before you hit an error page, not after
- The environment is kept in a usable state
-
When it wraps up
Hosting configuration taken back out, your setup restored in full
- The hosted account configuration is removed
- Desktop app and editor return to how they were
- Your original setup comes back
- Switch accounts by hand
- Adjust CLI, editor and desktop settings one by one
- Remember which settings were touched
- Tidy everything up afterwards yourself
- Worry about losing your own login
None of this affects this machine's signed-in state — you never have to sign in again.
Two platforms, four ways to use them
Claude and Codex are two separate subscriptions, each with its own account and environment. Within one platform, the CLI, editor extension, desktop app and web all share the same account — switch where you work and nothing else changes
Claude
Anthropic- claude.ai account hosting
Codex
OpenAI- chatgpt.com account hosting
Command line
The first-party Claude Code and Codex CLIs — install and go
Editor extension
Not just VS Code — Cursor and Windsurf too, and remote development environments as well
Desktop app
The desktop apps run on the hosted account; setup is automatic and yours can be restored at any time
Web app
One click from the console — nothing to configure
When you want a chat window, just open the web app
Not everything belongs in a terminal. Your hosted account comes with a web entry point in the console — click through and you are in the first-party chat interface, on the same account you use from the CLI and your editor.
- The first way in that works — no waiting on any further authorisation
- Nothing to install; just open a browser
- Available for both Claude and Codex
The web entry point is active for as long as the subscription is, and stops when the account expires.
Do you already have an account, or should we get one?
This decides what you pay and what you have to do. The difference is laid out before you choose — you will not pick one and then discover it needs an add-on
I already have a working account
- Cost
- Just the subscription. Hosting an account you already own costs nothing extra.
- What you do
- One sign-in through the wizard and you are done. Two things worth knowing first: it has to be an email sign-in, not "Continue with Google"; and we never ask for your password.
- How soon
- No waiting on us to source an account. You can start as soon as the environment is ready — how fast it goes is up to you.
- Good if
- You are not short of an account — you are short of a stable environment and someone keeping an eye on it.
I do not have an account yet
- Cost
- Subscription plus an account procurement pack. The account is paid for at official list price; we do not mark it up.
- What you do
- Tell us which plan you want. Signup and setup are done for you — just wait for the notification.
- How soon
- We open the account through official channels and let you know once it is ready. You can follow the status in the console meanwhile.
- Good if
- You would rather not deal with signing up and paying yourself, and want something that just works.
You can choose at any point after subscribing, or subscribe first and decide about the account later. One thing worth saying up front: if the account you bring is a free-tier one, only the web app will work — the CLI, editor extension and desktop app all need a paid account.
Subscription or pay-as-you-go?
These are not either/or — you can run both. The cases below should help you tell which one fits right now
FAQ
01 What does it cost?
Plan tiers and amounts are shown in the console subscription centre; we do not quote them separately on this site.
02 Does the wait before assignment count against my subscription?
No. Your subscription starts counting from the moment your dedicated environment is actually assigned to you, not from the moment you pay. The wait in between does not eat into the time you bought. And if the environment is adjusted later, the clock is not restarted.
03 Is account hosting actually free?
Hosting your own account costs nothing. The subscription fee pays for a dedicated runtime environment and the operational stack around it. If we procure the account for you, it is bought through official channels at list price — we do not mark up the account itself.
04 I want both platforms — do I need two subscriptions?
Claude and Codex are two separate subscriptions, each with its own account and environment, so using both means two of them. You can also start with just one and add the other later — they run independently, with their own expiry dates.
05 Why do the procured account and the base subscription expire on different dates?
A procured account follows the vendor's own monthly billing date; the base subscription follows ours. The two cycles are naturally offset and are never auto-aligned. The console shows both dates side by side and points out which comes first — renew each on its own date.
06 Why does the first sign-in have to go through the wizard?
This is the step that binds the account to your dedicated environment correctly, which is what makes everything after it go smoothly. The wizard prepares the environment for you — just follow the prompts.
07 What happens if the account runs into trouble?
Whether an account keeps working is ultimately the vendor's call, and we do not guarantee the account itself. But you will not be left guessing — the moment an account goes invalid the console flags it, offers a re-authorise link and sends a notification, so you never end up staring at an error page wondering whether it is your own network. When something needs doing, the console runs a check first and tells you plainly whether it is possible and what it would cost, then leaves the decision to you. Either way your dedicated environment stays reserved for you and the environment does not change.
Get your own Claude / Codex account
The account is yours, the environment does not move, and both cost and progress stay in the open