Atelier · loading…
Compare · Atelier vs Zapier
Zapier is a horizontal integration layer — it shines when you need to move a row from app A to app B. Atelier is a vertical orchestration layer purpose-built for teams that already operate on Perpetual Core products. Every Flow has first-class access to Sage skills, Sentinel verdicts, RFP drafts, Janice hires, and Catalyst purchases. Same identity, same tenancy, same trace timeline. You can still wire external webhooks when needed — but the deep integrations are native, not bolted on.
When to use Atelier
Your team runs on PC Studio products (Sage, Sentinel, RFP, Janice, Catalyst) and you want the playbooks you already follow to live as versioned, traceable, agent-augmented Flows your team can fork and improve.
See Atelier pricing →When to use Zapier
You need to glue together a long tail of third-party SaaS apps that don't share an identity layer or event bus — Slack to Notion to Google Sheets to Mailchimp to Trello. Zapier is the right call when "any-to-any" is the requirement.
General-purpose integration glue
Side by side
Feature
Atelier
Zapier
Native to Perpetual Core Studio (Sage, Sentinel, RFP, Janice)
First-class step kinds + shared identity
No native PC Studio integration
Agent-augmented steps (call an LLM with shared org memory)
sage_skill step kind, server-to-server
OpenAI / Anthropic actions via API key only
Human approval steps with checkpoint timeline
human_task step kind with assignment + checkpoint
Path conditions + manual approval (Pro plan)
Conditional gates on accumulated context
CEL-like expressions on run context
Path conditions on trigger payload
Event subscriptions across products with HMAC signing
Shared PC Event Bus with idempotency keys
Webhooks by Zapier (single-direction trigger)
Multi-tenant from day one (org-scoped RLS)
Per-org isolation enforced at the database
Single workspace per Zapier account
Full trace timeline (every step, every retry, every decision)
Append-only atelier_traces table
Task history with limited retention
Versioned Flow definitions you can fork across orgs
atelier_flow_versions with global library + per-org forks
Templates exist but no version history
Reusable templates curated by an operator
5 starter Flows shipped on day one — Catalyst, RFP, Onboarding, Review, Nurture
Marketplace templates (community-contributed)
Public API for external automation
Server-to-server today; first-party API in v1.1
REST API on Pro / Team plans
Cross-Supabase / cross-product tenancy bridge
pc_external_org_map handles Sentinel (separate DB) + external sources
N/A — Zapier is its own data plane
Per-run cost predictability
Fixed run cap per tier; $0.05/run overage
Task-based pricing tiers
On pricing
Zapier tiers (2026): Free 100 tasks/mo, Starter $29.99/mo (750 tasks), Professional $73.50/mo (2K tasks), Team $103.50/mo (50K tasks), Company $158.50/mo. Atelier Team ($399 / 2,500 runs / 5 seats) is more expensive per-task than Zapier Team, but Atelier runs are deeper — a single Atelier run can include Sage reasoning, human approval, and cross-product calls that would be multiple Zapier zaps stitched together. Tasks aren't comparable units.
Honest take
If your stack is broad and shallow — many SaaS apps, no shared identity — Zapier is the right choice and we'll happily integrate with it via webhooks. If your stack is centered on Perpetual Core and you want your team's playbooks to live as orchestrated, traceable, agent-augmented Flows, that's what Atelier is for.
Open a workspace
Atelier opens in fifteen minutes with five starter Flows and every Perpetual Core product already connected. Evaluate for fourteen days; bring your team when you're ready.