Step 1
Create account
Start on anonystack.com, then open the console on console.anonystack.com without linking a personal inbox or phone number.
AI builders
Give each AI agent a real inbox and isolated workspace in minutes
Stop routing automations through your personal inbox. Launch one identity per agent, give it a real @anonystack.xyz mailbox, and keep mail, notes, tasks, calendar, and kanban local to that identity.
Real mailbox per agentIdentity-scoped API tokensNo personal account linking
How it works
Create account, create identity, open inbox and workspace
The core product loop is intentionally short so you can get to an activated test quickly, then add shared planning or API tokens only when the workflow needs them.
Step 2
Create identity
Provision one isolated identity per agent, workflow, or customer stream and enable only the apps that identity needs.
Step 3
Open inbox and workspace
Use the identity mail inbox plus notes, tasks, calendar, and kanban as the operating layer for that agent.
Good fit
Who this is for
- AI builders who need a real inbox for agents instead of aliases or their personal email.
- Automation teams that want one isolated workspace per browser agent, customer flow, or task runner.
- Teams coordinating multiple agents that need a shared place for notes, tasks, calendar, and kanban.
Not the target
Who this is not for
- General consumer email replacement for personal communication.
- Enterprise procurement-heavy deployments that need long sales cycles and custom contracts before testing.
- Teams looking only for a kanban or notes tool without the identity and inbox model.
Use cases
Choose the workflow you need to isolate first
Each use case keeps the same core flow while changing where the boundary matters most.
Use case
Give every AI agent a real inbox instead of your personal email
Provision a dedicated @anonystack.xyz mailbox and workspace for each agent so email flows stay isolated from your own accounts.
- Dedicated @anonystack.xyz mailbox per identity.
- Mail, notes, tasks, calendar, and kanban stay scoped to the same identity.
- You can retire one identity without touching the rest of the account.
Use case
Run browser and email agents in isolated workspaces
Keep each browser or email automation in its own identity so credentials, inbox state, notes, and tasks do not leak across flows.
- Identity-scoped API tokens with per-app permissions.
- Mail and workspace data isolation by default.
- Token revocation and secret reveal flows already live in the console.
Use case
Coordinate multiple agents with shared planning and separate identities
Use isolated identities for execution and shared workspaces for planning when several agents need to contribute to the same outcome.
- Identity workspaces keep execution isolated.
- Shared workspaces support notes, calendar, and kanban collaboration.
- The dashboard already exposes both identities and workspaces under one account.
Proof assets
Use the existing seeded demo account to show the product fast
The repo already ships with seeded screenshots, demo data tooling, and written activation guides.
90-second walkthrough
Script and shot list for the branded product walkthrough using the seeded demo identity.
Open the inbox walkthroughScreenshot-ready console states
Real dashboard, mail, calendar, notes, tasks, and kanban screenshots already ship with the static site content.
See a screenshot-backed guideActivation guides
Use the published setup guides to move from account creation to the first active identity quickly.
Browse all guides