Indie marketing command

All your launches, one signal.

Pharos is the marketing operating room for small teams shipping many products: contacts, campaigns, automations, beacons, social, analytics, and revenue in one focused console.

Request early access See pricing

Command view

Launch pulse

Morning signal

Live

42.8k

subscribers synced

Social

posts queued

Beacons

127

mentions found

Revenue

$12.4k

monthly signal

Automation lane

Trial started

Wait 2 days

Send setup story

Skip if paid

Everything in the box

Eight surfaces, one project row.

Every app you ship keeps its own sender, branding, audience, automations and revenue view — without rebuilding the plumbing each time.

Campaigns

Templates with your branding baked in, per-recipient tokens, and English/Portuguese variants sent from one campaign.

Automations

Tag-triggered drip sequences with delays and skip rules. Your app tags a contact; the sequence does the rest.

Transactional

Receipts, results and alerts through one idempotent endpoint. Retry as often as you like — it sends once.

Beacons

Reddit, Hacker News and Bluesky watched for your product, collected into an inbox you can actually clear.

Revenue

App Store and Play figures synced per project — units, proceeds, active subscriptions, MRR. No estimates.

Reviews

Store reviews pulled in newest-first, filtered to the ones that are complaints, so a bad one gets answered.

Social

Queue posts and catch mentions across your connected accounts alongside everything else.

Deliverability

Every send is one row: delivered, bounced, opened, complained. Suppressions are permanent and protected.

Built for agents

Let a model draft it. It still can't send it.

Pharos is an API before it is a dashboard, so a coding agent can drive it directly. Point Claude Code at your workspace and it can write a campaign, resolve exactly who would receive it, and render the final HTML.

What it cannot do is deliver any of it. Sending is a separate scope that agent keys do not carry — so the guarantee lives in the credential rather than in a prompt, and holds no matter what the model decides to do.

Read the MCP docs

One command, nothing to install

$ claude mcp add pharos -s user -t http \
    https://pharosbase.com/api/mcp \
    -H "Authorization: Bearer pha_…"

Can

draft, preview, resolve recipients

Cannot

deliver a single message

Your sender, your reputation

Pharos drives your email. It doesn't send it for you.

Connect your own Resend or Amazon SES account. Mail leaves under your domain, on your reputation — never pooled with anyone else's.

Nobody else's bad week

Shared sending means one customer's bad campaign degrades everyone's delivery, and no way to give it back. Your credential, your control.

Consent that holds

Double opt-in on public forms, one-click unsubscribe on every list email, and hard bounces and complaints suppressed permanently.

Facts stay deterministic

Recipients, numbers and rankings are computed, never generated. The model writes copy; every generation is audited.

Launch playbook

From idea to audience without rebuilding the machine.

Import contacts from your app, Stripe, or a CSV

Write campaigns with product-aware context

Schedule drip sequences and win-back flows

Watch Reddit, Hacker News, and Bluesky for demand

Start here

Ten minutes from a key to a real send.

Or read the whole contract first — the docs are the same pages your agent gets.

Request early access Read the quickstart