People say "Agency OS" the way they used to say "all-in-one." That usually means a project tool with a marketing site. Felagar uses the phrase more narrowly: the operating system is the place where studio and client share the work, and where CRM, time, and approvals are not a separate product you sync at midnight.

Here is what that means, and what we are explicitly not.

What an Agency OS is

An operating system for an agency has to hold the messy middle:

  • A board the team actually moves
  • A client who can see status and approve work without joining your internal Slack
  • Intake that becomes a ticket instead of a form dump in email
  • Companies and deals next to delivery, so "won" can start a project
  • Hours and retainers next to cards, so margin is not a quarterly surprise
  • Optional AI that is grounded in that client's vault, not the open web

That is Command Center plus portal plus commercial context. Felagar's features catalog is organized around those jobs, not around a feature bingo card.

If you only needed Kanban, Trello was enough. If you only needed files, Drive was enough. The OS is the coupling: review state, chat, pulse, and billing-shaped facts in one tenant.

What Felagar is not

Not a social scheduler. Styrar is Athom's social OS. Felagar connects per client for planning, approvals, and "confirm before push." If you need a bio page and a link in bio, that is Styrar. Felagar does not pretend to be Buffer.

Not your accountant. Profitability views compose time and retainers. They do not replace the books. We will not invent survey stats about "agencies who switched."

Not Shopify Admin. The Shopify path is launch work on a Felagar project, then draft or publish to the client store. Merchants still live in Shopify.

Not a generic AI wrapper. Rad is vault-grounded and can be wrong. Confirm before anything reaches a client or Styrar. Self-host will be BYOK. Hosted AI is Felagar-hosted when you are on SaaS.

Not GA self-serve checkout today. Hosted Felagar is invite-only beta. Pricing shows what you pay when you are approved, not an open Stripe button that creates a live tenant for anyone with a card. The app host will be felagar.app when that path is live. Until then, request beta access.

Not self-host tomorrow morning. Core will be free to self-host when we publish that distribution. It is coming; it is not a download on the homepage.

Why the distinction matters

If everything is "OS," then every competitor comparison is noise. Compare Felagar to Productive, Teamwork, Basecamp, or ClickUp on delivery plus portal plus CRM plus time, not on who has more Gantt skins.

An Agency OS also has an opinion about agents. MCP is how Cursor or Claude join with agency permissions and an action audit. That is part of the OS, not a novelty chatbot in the corner.

What "one workspace" is allowed to omit

A serious OS still has edges. Email can be a channel into tickets and chat. Slack can post. Figma can import into review. The OS owns the decision and the record. The other tools own their native craft.

If a vendor claims they replaced Slack, Figma, Shopify, your bank, and your lawyer, they are selling a story. Felagar's job is the agency record: company, project, approval, hour, file, pulse. Integrations keep the craft tools. That boundary is why we bother with the OS label at all.

Access is not a slogan

An Agency OS is also a commercial promise. If the homepage says start free and checkout is a waitlist, that is a trust problem. Hosted Felagar is invite-only beta: you request access, we approve in batches, then you pay the plans on Pricing. That is not an open buy button. When GA lands, register will live on felagar.app. Until then, treat the price table as what you will pay when approved, not a self-serve checkout.

Command Center is the staff home for what needs attention across companies you can see. It is not a fourth inbox. If everything pages you, nothing is an OS. Triggers should fire for waiting reviews, quiet accounts, and burn, then get out of the way.

How to evaluate us without the slogan

Ignore the phrase. Ask:

1. Can a guest approve a deliverable without a full account? 2. Can the studio see waiting reviews and burn without exporting? 3. Does the client portal wear the agency (and optionally the company) brand? 4. When a deal is won, can you start from a template instead of a blank board?

If the answers are yes, you are looking at an OS. If they are "we have an integration," you are looking at a tool pile.

Also ask who owns onboarding after you win. A checklist plus a client wizard that seeds the vault is OS-shaped. A welcome email with twelve links is not.

Read the changelog for what actually shipped. Request beta access if you want to run a studio in one hosted workspace. That is the honest version of Agency OS: partners who share the work, not five tabs that almost talk.

Related