1Create your account
Go to cloudstack.aeorbit.com/register and sign up with your email or with Google. Every new account starts on the Free plan: 1 client, 1 campaign and 50 pages a month. No card needed.
2Add your API keys
Cloud Stack uses your own keys, so usage is billed by each provider directly. Open Settings → API Keys and add at least one key from each required group. Keys are encrypted before they're stored.
| Group | Add one of | Used for |
|---|---|---|
| Content generation (required) | OpenAI, Google Gemini or Anthropic Claude | Writing every page from its brief |
| SERP & competitor analysis (required) | DataForSEO (login:password) or SerpAPI | Studying what ranks in each city |
| Geo research (required) | Google Places API | Neighborhoods, landmarks and local detail |
| Housing data (optional) | US Census API | Housing facts per ZIP code |
3Connect a cloud account
Open Settings → Platforms and add a storage account. Choose the platform, give it a display name (for example "Client A, AWS primary"), pick a region if the platform asks for one, and paste its credentials.
- You can add several accounts per platform, for example one per client.
- You don't need to create buckets in advance. Cloud Stack can create one per campaign for you.
- Supported: Amazon S3, Google Cloud Storage, Azure Blob, DigitalOcean Spaces, Netlify, Linode, Vultr, Wasabi, Backblaze B2, Oracle Cloud and IBM Cloud.
4Add a client
Go to Clients → Add Client and fill in the business details. The more accurate this is, the better every page will be.
- Business info: name, website, phone number and domain. The phone number is used on every page and checked before deploy.
- Google Business Profile & socials: optional, used for trust signals.
- Images: upload photos of the team, vehicles or past work to use on pages.
When a campaign runs, Cloud Stack also reads the client's website to pick up their services, brand and proof points.
5Create a campaign
Open Campaigns → New Campaign and set it up:
- Name and client: for example "FloodPro Dallas Q1".
- Services: the services this campaign should cover.
- Service areas: the cities to build pages for.
- Page counts by type: how many pages of each type to build. The preview shows the total.
- Custom pages (optional): extra pages such as an FAQ page, About us or Testimonials.
- Cloud configuration: choose platforms and accounts, set how pages are split between them (shares add up to 100%), and pick Automatic buckets or choose your own.
Save the configuration. Cloud Stack validates the campaign and shows an estimate before you run it.
6Run, review and publish
Start the run. You can follow every step live in the Pipeline monitor: research, writing, checks and deploy. If you're already running as many campaigns as your plan allows, the new run waits and starts by itself when a slot frees up.
- Review: preview pages, browse them by type, and check Quality flags and Similarity for anything that needs attention.
- Fix: regenerate a single page, or retry only the pages that failed.
- Publish: pages deploy automatically at the end of a run. You can re-deploy to a bucket later, and the sitemap is generated with every run.
- Share: export every live URL as CSV or JSON for reports, or submit the sitemap to Google Search Console.
Use it from Claude or ChatGPT
Cloud Stack has an MCP connector, so you can run campaigns by chatting with your AI assistant. Open Settings → MCP in the app for the exact setup steps for each client: Claude, ChatGPT, Claude Code, VS Code, Cursor, Windsurf, Gemini CLI and Codex CLI.
Once connected, you can ask things like:
- "List my clients and their campaigns."
- "Create a campaign for RoofCo: roof repair in 25 Texas cities, deploy to AWS. Estimate it first."
- "What failed in the FloodPro campaign, and how do I fix it?"
- "Export every live link for the Austin campaign as CSV."
Assistants and scripts that use tokens instead of signing in can get one from Settings → Access tokens.
Troubleshooting
"Required API keys not configured"
Add at least one key from each required group in Settings → API Keys (see step 2).
A run failed partway through
Open the run in the pipeline monitor. The error tells you the next step: resume (a temporary problem), update API keys (a key expired or ran out of credit), fix cloud account (credentials or bucket access), or fix campaign. Once it's fixed, resume the run. Finished steps aren't repeated.
"Your plan allows N pages/month"
The run would go over your monthly page budget. Make the campaign smaller, wait for next month, or upgrade.
Some pages have quality flags
Flags explain what's wrong, for example two pages that are too similar or an FAQ answer that's too short. Regenerate the flagged pages. Pages with blocking problems aren't deployed until they pass.