The open-source visual platform for Astro. Build responsive pages, manage content with a complete CMS, define a shared design system, and control technical SEO. Aria includes a built-in AI agent with bring-your-own-key support and MCP for external tools. Full access from day one. No feature tiers. No lock-in.
Quick start ⌁ Runtimes ⌁ Capabilities ⌁ Docs ⌁ Contributing
Deploy Aria to Cloudflare in one click, or run it locally with Node and SQLite.
- Click the Deploy to Cloudflare button above.
- Accept the generated resources. Give the two KV namespaces distinct titles (e.g.
aria-cacheandaria-session) - the automatic deployment cannot prefill those. - Open
/adminon the live site, create your first administrator, and complete first-launch.
Details, prerequisites, and manual deploy: Cloudflare deployment guide.
Requires Node.js >= 22.18.0 and npm.
git clone https://github.com/ariabuilder/aria.git
cd aria
npm install
npm run devFor Cloudflare bindings locally, use npm run dev:edge.
Open http://localhost:4321/admin and finish setup at /admin.
After you attach a Cloudflare-managed custom domain, you can show zone traffic inside Aria. Setup: Cloudflare deployment guide.
Local setup · Edge development
| Cloudflare | Node + SQLite | |
|---|---|---|
| Runs on | Workers with D1, KV, R2, Queues, Durable Objects, and optional Workers AI | Your PC, VPS, Docker, Railway, or another Node host |
| Best for | Edge delivery and Cloudflare-native services | Local development, self-hosting, and straightforward deployments |
| Start with | npm run dev:edge locally; npm run deploy for production |
npm run dev |
The same Astro project, Astro Actions, and StorageAdapter run in both modes.
See storage and runtimes
for the architecture and trade-offs.
| Capability | What it enables |
|---|---|
| Studio & Composer | Edit the real page on a visual canvas, with Inspector controls, responsive viewports, and optimistic updates. Explore Composer → |
| CMS & collections | Define structured content, schemas, templates, relations, drafts, and revisions without a separate CMS product. Explore collections → |
| Design system & motion | Author tokens, semantic classes, fonts, and motion visually; publish only the CSS each page needs. Design system → Motion → |
| AI Engineer & MCP | Plan, create, and publish with an agent and external tools that honor the same role permissions as Studio. Explore Agent & MCP → |
| Site API | Connect site-local automations through policy-aware REST endpoints for CMS collection and entry workflows. Site API credentials are scoped to the site and use Aria's authorization model. |
| Auth & security | Use sessions, TOTP, roles, capabilities, audit logging, rate limiting, and login protection built into Aria. Authentication → Security → |
| Send password resets and transactional messages through Cloudflare Email, SMTP, or a local preview sink. Explore email → | |
| SEO & publishing | Publish with sitemaps, feeds, redirects, JSON-LD, crawler guidance, and site-health tools. SEO → Publishing → |
| Runtime & storage | Keep code portable while choosing SQLite locally or Cloudflare D1, KV, and R2 at the edge. Storage and runtimes → |
| Ownership & export | Download a clean Astro project, including your pages, components, design system, and CMS data. Export and import → |
The job has not changed: ship a site, manage content, and iterate on design.
Aria Builder combines visual editing with an Astro codebase and a runtime you control.
| The old way | Aria | |
|---|---|---|
| Foundation | Theme and plugin layers across several products | One Astro project with Studio, content, design, and publishing |
| Content | A posts table plus add-ons | Structured collections with schemas and visual templates |
| Design | Theme options that drift | A canonical design system shared by previews, publishing, and export |
| AI | A disconnected chat sidebar | An agent and MCP server with the same capabilities as a user |
| Ownership | Hosting and export restrictions | A project you can run, deploy, and export yourself |
Aria separates code deployment, schema migrations, and content promotion.
A builder update does not overwrite live pages or settings unless you
explicitly promote content.
The Studio export creates a clean Astro project you can take elsewhere. For deployment, media storage, content promotion, and environment configuration, use the Cloudflare deployment guide, content-sync guide, and environment-variable reference.
Technical details for contributors, including the generated inline-SVG icon pipeline, are documented in the platform architecture.
Aria is pre-launch and under active development.
Webhook automation, third-party OAuth, Figma integration, and plugins are not currently available and are currently being developed.
See ROADMAP.md for publicly planned work.
Start with Aria docs for setup, deployment, Studio workflows, and contributor architecture.
Documentation will be expanded on as we progress with development. Expect full step by step guides, video tutorials, and more.
| Resource | What it covers |
|---|---|
| Deployment | Cloudflare setup, migrations, bindings, and content after deploy |
| Architecture | Platform boundaries and extension points |
| SECURITY.md | Private vulnerability reporting |
| TRADEMARKS.md | Name, logo, and fork-branding rules |
Contributions are welcome. Read CONTRIBUTING.md, review the contributor documentation, and open an issue before substantial architectural changes. Support expectations are in SUPPORT.md.
Bundled front-end asset notices, including Outfit under the SIL OFL 1.1, are listed in Acknowledgements.
Built for creators.
Apache-2.0 | See LICENSE | Trademarks | Acknowledgements