Your buyers. Your account. Your keys.
Anthosting runs the buyer lifecycle inside your own Phala Cloud account.
Private pilot. Buyer only.
One encrypted connection. One selected workspace. One measured buyer.
The account stays yours.
Anthosting manages the software.
| Layer | Owner | Anthosting |
|---|---|---|
| Provider account and bill | You | Never creates or pays it. |
| Workspace | You | Binds one selected workspace. |
| Buyer key | The CVM | Derived there. Never exported. |
| Funds and operator | Your wallet | Never signs or withdraws. |
Three moves to a running buyer.
- 01
Connect your Phala account.
Enter a scoped API key. Choose one workspace.
- 02
Deploy the buyer.
Provision through your connection. Require exact app, compose, and workspace readback.
- 03
Authorize and fund.
Your wallet sets the operator, verifies getOperator on Base, then deposits.
The key stays in the measured runtime.
Anthosting cannot take custody of funds or read the buyer key.
- Buyer key
- Derived inside the CVM. Never exported.
- Operator
- Your wallet. Funding waits for getOperator(buyer).
- Funds
- Base deposits. Only your operator can withdraw.
- Runtime
- TDX quote binds tenant, buyer, app, compose, and OS image.
Private buyer pilot.
One CVM you own, one buyer, up to 2 USDC.
Wallet and Phala account required.