Raytha v2.0.1: fixes for routes, functions, and sign-in
A patch on 2.0.0: route paths, Raytha Functions, SSO, list views, and email. There is no database migration.
Model your content, design with Liquid, publish through a headless REST API, and extend with JavaScript. Or hand the CLI to an AI agent and describe the site you want. One MIT-licensed app, one Postgres database, zero lock-in.
docker run -p 8080:8080 raythahq/raythaFree and open source forever. Self-hosted on your own infrastructure.
Install the Raytha CLI, give your coding agent an API key and a brief, and it builds the theme, the content model, the content, the pages and the navigation. Every command prints JSON, the manual ships inside the binary, and raytha check tells the agent when it is done.
$ curl -fsSL https://raytha.com/cli/install.sh | sh
$ export RAYTHA_URL=https://your-site.example.com
$ export RAYTHA_API_KEY=...
$ raytha doctor
> Build a complete website for Kiln & Kettle, a pottery
> studio and tea room. Theme, content model, seed content,
> pages, navigation. Finish with `raytha check`.
$ raytha check
{"ok":true,"data":{"checked":88,"failed":0}}
Raytha is deliberately small: one .NET app and a Postgres database. Everything you need to build and run a content site ships in the box.
Define the fields you need: text, rich text, dropdowns, relationships, files. The admin and the API follow automatically.
Every content type gets a REST endpoint. Authenticate with an API key and build any front end.
Layouts, partial views and widgets in the Liquid language you already know. Every change keeps a revision.
Give editors a page builder without giving up your design system. Widgets are plain Liquid with a settings form.
Serve sitemap.xml, handle webhooks, call APIs, send email. Plain JavaScript on V8, no deploy step.
SAML and JWT for admins and public users, plus roles, permissions and user groups.
Roll back content and templates, and see who changed what.
No build pipeline to learn. Deploy, model your content, and start publishing.
# Option 1: Railway (recommended)
# Open the template, click Deploy, wait a minute.
# Option 2: Docker
docker run -p 8080:8080 \
-e ConnectionStrings__DefaultConnection="Host=db;Database=raytha;Username=postgres;Password=..." \
raythahq/raytha
GET /raytha/api/v1/ContentItems/posts?pageSize=2 HTTP/1.1
X-API-KEY: your-api-key
{
"result": {
"items": [ ... ],
"totalCount": 42
},
"success": true
}
{% for post in Target.Items %}
<article>
<h2><a href="/{{ post.RoutePath }}">{{ post.PrimaryField }}</a></h2>
<p>{{ post.PublishedContent.summary.Text }}</p>
</article>
{% endfor %}
function get(query) {
const pages = API_V1.GetSitePages("", "", 1, 100).Result.Items;
const urls = Array.from(pages).map(p => "<url><loc>" + CurrentOrganization.WebsiteUrl + "/" + p.RoutePath + "</loc></url>");
return new XmlResult("<urlset>" + urls.join("") + "</urlset>");
}
curl -fsSL https://raytha.com/cli/install.sh | sh
export RAYTHA_URL=https://your-site.example.com
export RAYTHA_API_KEY=your-key
raytha doctor
# then, to your agent:
# "Read `raytha guide build-a-site` and build me a site for ..."
The Raytha CLI pulls a theme into a folder, lets you edit with your editor, and pushes it back. Content types, content, pages, menus and functions work the same way. Every command speaks JSON with exit codes you can script against, in a terminal or in CI.
$ raytha doctor
$ raytha theme pull my_theme ./site
$ raytha theme push ./site --dry-run
$ raytha theme push ./site
$ raytha site-page create --title About \
--template rt_page --route-path about
$ raytha check
Raytha is self-hosted. Pick the path that fits.
The fastest way to a running site. One click deploys Raytha with PostgreSQL, a domain and TLS.
Deploy on RailwayRun the published image anywhere you have Docker, with your own PostgreSQL.
docker run -p 8080:8080 raythahq/raythaClone the repository, build with the .NET 10 SDK and run it as a regular ASP.NET app.
View on GitHubA patch on 2.0.0: route paths, Raytha Functions, SSO, list views, and email. There is no database migration.
One binary that manages a Raytha site as JSON, built so an AI agent can build a website from a brief.
A new design for raytha.com, with the developer docs and user guide rewritten for Raytha 2.0.
Yes. Raytha is released under the MIT license. There is no paid tier, no feature gating and no hosted version to subscribe to.
Raytha is an ASP.NET app on .NET 10 with PostgreSQL as its only database. Run it on Railway, with Docker, or on any server that can run .NET.
Yes. Every content type is available through the REST API v1 with API-key authentication. You can also render public pages with Liquid at the same time.
Yes. Install the Raytha CLI where your agent runs, give it an API key, and describe the site. The CLI prints JSON, carries its own manual (raytha guide build-a-site), dry-runs changes and checks every route when it is done. It works with Cursor, Claude Code, Codex and any agent that can run a shell. Here is the walkthrough.
Yes. Professional consulting and support are available. Get in touch.
Deploy in minutes, by hand or by agent. Own your content and your code.