Account setup & plans
This guide covers creating an Aimly account, completing authentication and onboarding, understanding plan quotas, and preparing your workspace for outreach.
1. Create and verify your account
Register at aimly.online using either an email address and password or Sign in with Google.
Password registration requirements
If you register with a password rather than Google sign-in, your credentials must meet the following rules:
- Username — minimum 3 characters; letters, digits, and underscores only (
a–z,A–Z,0–9,_). - Password — minimum 8 characters, including at least one uppercase letter, one lowercase letter, one digit, and one special character.
- Email verification — Aimly sends a confirmation link valid for 48 hours (with a 60-second resend cooldown). You must confirm your email address before signing in with a password.
Accounts created with a password sign in with email and password; accounts created with Sign in with Google authenticate exclusively through Google and have their email verified automatically. When registering with a password, you can optionally choose an avatar and an interface theme (Ocean Mist or Autumn Brew).
Account approval and 14-day trial
New registrations stay in an Awaiting approval state until an admin approves them, which requires a free cohort seat. Once approved, your account automatically starts a 14-day free Trial (no credit card required) with Solo-tier limits so you can test the full suite immediately.
2. Subscription plans and quotas
Aimly plans govern active brands, active campaigns, and rolling 30-day lead discovery volume. Sending mailboxes are unlimited on every plan.
| Tier | Brands | Active campaigns | Lead discoveries (per rolling 30 days) | Mailboxes |
|---|---|---|---|---|
| Trial (14 days) | 1 | 10 | 500 companies | Unlimited |
| Solo | 1 | 10 | 500 companies | Unlimited |
| Studio | 5 | 25 | 1,500 companies | Unlimited |
| Agency | Unlimited | Unlimited | 5,000 companies | Unlimited |
How quotas are counted
- Archived campaigns do not count toward your active campaign limit. Archiving a completed campaign frees its slot immediately while preserving historical records.
- Lead discovery counts distinct companies, not individual contact rows. When Aimly Finder discovers multiple contacts at the same company during a search, those additional contacts (
+N extra) do not consume extra discovery quota. Rejected candidates never consume quota. - Plan downgrades — if your account holds more brands or campaigns (archived campaigns included) than a newly selected plan permits, product actions pause behind an Account action required remediation screen until excess brands and excess campaigns are deleted; archiving a campaign does not clear this screen.
3. Initial workspace checklist
Once signed in to aimly.online/dashboard:
- Configure third-party keys (optional for template outreach; required for AI features and Finder) — open Integrations in the left sidebar to add an AI provider key, web search keys, and optional ZeroBounce verification. See AI, Search & Verification.
- Create a brand — open Aimly Email → Brands and define your business name, description, and optional logo. See Brands.
- Connect a sending mailbox — open Aimly Email → Mailboxes to connect Gmail, Outlook, Yahoo, or a custom SMTP/IMAP server. See Mailboxes and Email provider integrations.
- Run a baseline audit — open Aimly Audit and test your connected mailbox to verify SPF, DKIM, DMARC, and inbox placement before launching outreach. See Audit.
4. Optional: generate an MCP API key
You do not need an Aimly API key to use any web dashboard. Generate an API key only if you are connecting an external MCP client via Bearer token rather than browser OAuth:
- In the unified dashboard (aimly.online/dashboard), select API Key in the left sidebar (or from Aimly Email, open your profile menu in the top right and choose Account → API Key).
- Click Generate API Key and copy the
aimly_...token immediately — it is displayed only once.
An Aimly API key grants full account access across Email, Audit, and Finder. Transmit it only in an Authorization: Bearer header over HTTPS, never expose it in client-side code or version control, and click Revoke or Regenerate immediately if compromised. Key generation is rate-limited to one request per 60 seconds and three generations per hour.