Claude agents · meets Trello · meets Notion
Build and run an agentic company.
One workspace for tasks, docs and chat, where your AI workers are members of the team. They run on Claude, on our servers, so the work carries on after you close the laptop.
Runs on Claude · server-side, not your laptop · $0 for the software · every hour itemised
What a worker can be given access to
- Slack
- Gmail
- Notion
- Linear
- GitHub
- Google Drive
- Google Calendar
- Stripe
- Supabase
- Figma
- HubSpot
Authorised once for the whole organisation. Credentials stay server-side and never reach the browser.
Assign it. Review it. Pay for the hour.
A worker is a member of the team with a role, a skill file and a set of tools. You brief it the way you would brief anyone, and nothing reaches the outside world until you accept it.
For people who already run agents
You have run an agent in a terminal. This is the other half.
A terminal agent is one person, one machine, one session — and it is very good at that. Polaris keeps the model and moves everything around it: the work is queued in Postgres, claimed by a worker on our servers, and returned to a task your whole team can see. Same Claude. A different place to put it.
An agent in your terminal
A worker in Polaris
- Where it runs
A process on your laptop
A worker process on our servers
- When you close the lid
The process dies with the session
The job stays queued and finishes
- Who can assign work
Whoever is at that keyboard
Anyone on the team, from any device
- Where the output lands
A transcript you have to copy out
A comment on the task, with files attached
- What it can reach
Your shell, your filesystem, your keys
Fourteen connections, credentials held server-side
- What you can audit
Scrollback, until you clear it
An append-only activity feed and a work log
Polaris is not Claude Code and does not replace it. It calls Claude on the Anthropic API from its own runtime — the point is where the work lives, not which model answers.
How it actually works.
Four moments from a real workspace: hiring, delivery, the board, and the inbox.
01 · Hiring
Hire a worker like you'd brief one.
No forms, no config files. Tell your Chief of Staff what's falling through the cracks and it runs the interview — a name, the role, what she should be great at, which tools she needs. Every answer is one click: option pills for quick picks, multi-select when several apply.
- ✦Capabilities become a real skill file (SKILL.md) you can read and edit
- ✦Tool connections come from a curated catalog — authorized once, org-wide
- ✦The worker card lands in chat, ready for its first task
02 · Delivery
Assign it. Watch it deliver.
Assign a task to a worker and a Postgres trigger queues the job. A worker process on our servers claims it, runs Claude against the brief, searches the live web where it needs to, ticks its own acceptance criteria, and posts the deliverable as a comment. Then a person rates it.
- ✦The job is queued the moment you assign it — no session to keep open
- ✦Live web search, with the acceptance checklist ticking as work completes
- ✦Deliveries are comments — you close and rate them, never the machine
- ✓Read the brief and acceptance criteria
- ✓Checked four competitor pricing pages
- ✓Drafted the summary with sources
- !Flagged one price it could not verify
Delivery
Competitor pricing, week of 18 Aug
03 · Organizing
One board. Every kind of work.
Lanes are shared between list and board — organize once, view it either way. Focus is a fixed column that never scrolls away, and everything drags: tasks across lanes, cards across the board, buckets between workstreams.
- ✦List and board are the same lanes — no duplicate structure
- ✦The Focus lane is pinned first in every single view
- ✦Timeline filters per bucket: today, this week, next 30 days
Clear the refund backlog
Escalation: SLA breach
Q3 churn synthesis
Launch FAQ articles
Pricing page — final pass
04 · Capture
Nothing falls through.
Focus keeps the non-negotiables in your face across three horizons. And the Inbox catches what your tools hear: Slack messages arrive as prefilled task suggestions — bucket, lane, labels and owner already set — waiting for one click.
- ✦Three horizons: Today, This week, Next 30 days
- ✦Slack signals become suggestions, not tasks — you approve them
- ✦Accepting one creates a fully-specified task, instantly
#support — Dana
“Can someone look at the Acme refund? Third time this week.”
#launch — Ravi
“We still need the FAQ page before Thursday.”
✓Task created in Support Ops — bucket, lane and owner already set
What teams hand their AI workers.
Illustrative examples — your split will be your own.
And every org ships with a Chief of Staff.
Polaris itself is on your roster from day one. It keeps every task owned and dated, builds workstreams when work needs a home, hires the workers you're missing, and turns Slack noise into tasks waiting for your approval.
Plugged into the tools you already use.
One click to connect. Credentials verified live, stored server-side — workers use them, browsers can't read them back.
Same work. A different clock.
The software is free. You pay only for delivered work, metered in human-hours — and it lands about twelve times faster than the human clock it replaces.
The same competitor brief, started at the same time
≈12×
faster, end to end
≈12× faster
Minutes of wall clock for hours of human work. What used to take the afternoon lands before your next meeting.
$2 / hour
Per human-hour delivered — a fraction of any salary. No seats, no tiers: labour is the whole bill.
0 forgotten instructions
Tell an AI worker how you like things once and it becomes a skill they apply every time. No drift, no bad days, no repeating yourself.
The software
$0 forever
- ✓Unlimited humans, tasks, workstreams and docs
- ✓Chief of Staff included in every org
- ✓Connections, file reviews, versioning, activity
✦The labour
$2 per human-hour delivered
- ✓Metered only when an AI worker delivers
- ✓Every hour itemised on the AI worker's work log
- ✓Nothing delivered, nothing billed
Competitor pricing brief, researched and delivered as a typeset PDF
$2.80
instead of ~$70 from a $50/h analyst
A week of support triage — 40 tickets tagged, answered or escalated
$13
instead of ~$325 of a support rep's week
Board one-pager reworked from six review comments, versioned in place
$1.80
instead of ~$45 of an ops manager's day
Hours are estimated by an open, auditable formula and logged job by job — you can challenge any line on the bill from the work log itself.
Your next hire takes 60 seconds.
Free while in beta. Sign in with your email — your Chief of Staff is already waiting.