Every client site. Every brand. One console.

Two ways of running many sites, and one place to run them. The film follows an agency running twelve client sites and a company running five brands, and what changes for each when every site lives in one Aglyn console.

What follows is the longer version — what each setup actually looks like, and where every piece of it lives.

An agency running twelve client sites

Twelve client sites used to mean twelve logins and twelve bills, with nothing shared between them. In Aglyn it is one org, one console and one bill: a host per client under your org, each with its own domain, plan and traffic.

The host is the unit of separation. A client's pages, media, forms and contacts belong to that host, so nobody working in one is looking at another — and for agencies, white-label means what the client does see carries your name rather than ours. Single sign-on and audit logs cover your own side of it.

Pages are built on a live canvas in Besigner, where what you see is what ships — real components, your theme, your content. There is no separate staging build to reconcile, because the canvas is the page. Checkout, subscriptions and point of sale sit on that same page: products, checkout, subscriptions and digital goods, with no second platform to bolt on.

Publishing puts a site live on the client's own domain, with SSL and global delivery. Every publish is a version, so undoing a change is picking the version before it rather than restoring a backup — which is what makes handing a client edit access survivable.

A company running five brands

With five brand sites, every form used to land somewhere different. In Aglyn the site fills in the CRM: a form files a lead, a sign-up a subscriber, a purchase a contact — automatically, with no import, no sync and no second tool.

That makes the five brands one audience, emailed from one console. Design the email on the same canvas the pages are built on, send it to a list your forms and orders already filled, then read the opens and clicks beside the pages that earned them.

An interaction fires an event and the follow-up runs itself: contact created, stage changed or deal won can trigger the email, the task or the Slack post. Nothing is copied between systems, because there is only the one system.

A brand site goes from start to finish in an afternoon, in the same console, and each brand keeps its own domain, its own theme and its own numbers.

What the film has no room for

Media, plugins and analytics are shared across every site in the org and already in there. There is nothing to integrate and no other vendor to pay: every product reads the same sites, the same audience and the same data, which is the whole reason a form can reach the CRM without a connector in between.

It also means the bill is one bill. The cost of running twelve sites is a plan per host, not a plan per host multiplied by the four tools each of them used to need.

Running one site

It works exactly the same way — the org, the host and the console are the same shapes whether there is one site under them or twelve. Self-host it under Apache-2.0, or start free today.