Pricing
Simple, like a cat's needs
Free during the beta — desktop and cloud. Simple, indie-sized plans land with 1.0.
Pricing
Runs on your machine. Beta is on the house.
Desktop
Free
During the beta
- The full engine, all local
- Your Claude Code / Codex login
- Schedules, queues, experiments
- Community Discord
Cat Cafe
$0
Invite-only beta
- Always-on cron + queues
- One workspace, 3 seats
- KMS-encrypted credential vault
- Same engine as Desktop
Pride
Custom
For real teams
- Everything in Desktop + Cloud
- SSO + audit log
- Priority email support
- Annual contract
The beta · joining the cafe
Desktop builds go out by invite while we roll the beta forward — email [email protected] with a one-liner about what you're building and we'll send you one. Cloud invites open once the always-on parts finish burning in.
FAQ
Questions the cat anticipated
Can I run Pallas without the cloud?
Yes — that’s the default. The desktop app is the whole product: local database, agents, schedules, queues, experiments. The cloud is an optional always-on companion for runs that shouldn’t wait for your laptop lid.
Do I need API keys?
No. Desktop agents drive the coding-agent CLIs you’re already signed into — Claude Code, Codex, and friends — so there are no keys to manage and no tokens resold. The hosted cloud runs on managed keys instead.
What about my data?
On desktop, every workspace byte lives in a local database under your user directory, encrypted with a key held in your OS keychain, with a telemetry kill-switch. Our server only ever sees your login. Your strategy also round-trips as markdown to a GitHub repo you own.
Will it spam my prospects?
No. Outreach is human-gated: agents research and draft, you review and send. Compliance checks run before anything leaves, and re-contact rules stop repeat pings to the same person.
Why the cat?
Pallas the asteroid, Pallas the goddess, and Pallas’s cat all share a name. The cat won the branding meeting.
When can I actually use it?
The desktop beta is rolling out now — email us for an invite. The hosted cloud stays invite-only while we burn in the always-on parts.