Why Aglyn is Apache-2.0
Your website is not a thing you should rent. It carries your content, your customers, and a growing share of your business — and if the platform under it disappears or changes its terms, you should be able to walk away with everything intact. That's why Aglyn is Apache-2.0.
Your website is not a thing you should rent.
What the license buys you
Apache-2.0 is a permissive license with an explicit patent grant. In practice it means you can read the source, run it commercially, modify it, and fork it — without asking us. The code is public on GitHub, and the version you self-host is the same platform we run as a service.
Self-host it
Aglyn ships with Docker-based self-hosting and a bring-your-own-Firebase setup. If you outgrow our hosting, disagree with a decision, or simply have compliance reasons to run on your own infrastructure, that door is open by design.
Extend it
Openness isn't only the license. The plugin platform lets you add blocks and behaviors to the editor, the marketplace distributes them, and the REST API reaches your content from outside. The extension points we use to build Aglyn's own features are the ones you get.
Open source as accountability
An open codebase keeps us honest: our security posture, our data model, and our roadmap all happen where users can see them. Early access will change many things — the license is not one of them.
Share this article
Zach Gover is the founder and CEO of Aglyn. He spent eighteen years on both sides of the marketing–engineering handoff — building sites as a contractor, then running technical marketing at Caringo through its acquisition by DataCore and at DuploCloud from seed through Series B. The pattern never changed: the marketing site is a company’s most-visited product surface and the one the team can least afford to touch. Aglyn is his answer to that. He writes from Austin, and this site is built in the product it describes.