Atelier · loading…
Compare · Atelier vs Asana
Asana is a work-management surface — projects, tasks, assignees, due dates, status. It assumes humans execute the work and the tool keeps everyone aligned on who owns what by when. Atelier is the layer below: your Projects hold Flows that orchestrate Sage skills, cross-product actions, and human checkpoints into traceable runs. Many ops teams use both — Asana for the human-coordination surface, Atelier for the operational playbooks that the team executes again and again.
When to use Atelier
You have repeatable operational playbooks (Catalyst delivery, RFP response, intern onboarding, donor nurture, curriculum review) and you want them to live as versioned Flows that combine Sage reasoning, cross-product actions, and human approvals — not as task lists that have to be re-created every time.
See Atelier pricing →When to use Asana
You're coordinating a cross-functional team on bespoke, mostly-human work — marketing campaigns, product launches, client deliverables — where the value is in shared visibility on tasks, owners, and dates rather than in repeatable orchestration.
Work management for cross-functional teams
Side by side
Feature
Atelier
Asana
Native to Perpetual Core Studio (Sage, Sentinel, RFP, Janice)
First-class step kinds + shared identity
Generic work management; no PC integration
Agent-augmented steps (LLM with shared org memory)
sage_skill step kind, Sage Mnemosyne writes
Asana Intelligence writes task summaries / status updates only
Cross-product event triggers (Sentinel verdicts, RFP draft ready, etc.)
event_wait + PC Event Bus with HMAC envelope
Rules engine on tasks + third-party integrations only
Conditional gates that branch on accumulated context
gate step kind evaluates expressions on run.context
Rules are if-this-then-that on task fields; no run context
Task / project tracking with status / assignee / due date
Projects + project members + human_task steps
Asana's native domain — best-in-class
Portfolios + goals + workload + timeline / Gantt
Not the focus — pair with Asana for cross-team portfolios
First-class portfolio / goals / timeline views
Reusable templates / playbooks
Versioned atelier_flow_versions with global library + per-org forks
Project templates (no agent steps, no event triggers)
Multi-tenant by org (RLS-enforced isolation)
Every row carries org_id; pc_runtime role enforced
Workspace-level isolation per Asana account
Trace timeline with every step / agent call / human action
atelier_traces append-only, queryable via SQL
Activity log per task
Per-run cost predictability (LLM + agent calls)
Run-based pricing tier; $0.05/run overage
N/A — no LLM or agent runtime in the priced unit
Public API for external automation
Server-to-server today; first-party API in v1.1
REST API + webhooks since 2010s
Cross-functional people-coordination surface
Operator-led — built for playbooks, not bespoke human work
Asana's differentiator — shared visibility for cross-functional teams
On pricing
Asana tiers (2026): Personal Free, Starter $10.99/user/mo, Advanced $24.99/user/mo, Enterprise contact, Enterprise+ contact. Atelier per-seat prices are higher because each seat carries the LLM + cross-product runtime, not a coordination surface. Most ops-heavy teams use both — Asana to coordinate the humans, Atelier to run the playbooks the humans launch.
Honest take
If your team's primary problem is "who owns what by when across cross-functional work," Asana is the right surface. If your team also has recurring operational playbooks — onboarding, capture ops, delivery, nurture — and you want those to live as versioned Flows your team can fork, that's what Atelier is for. They're complementary.
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.