Two ways to use AstroBaaS

AstroBaaS works in two quite different ways, and you can switch between them without moving your content.

1. As a normal website

Write posts and pages in the admin and they appear on your site immediately — there is no rebuild and no deploy step. Pages are rendered on the server, so a visitor gets finished HTML and very little JavaScript: a cookie-consent manager, and the AI assistant if you switch it on.

2. As a backend for your own front end

Point any site at the API and use AstroBaaS purely for content, products, orders and files. The next post covers this in detail.

Extending it

• Plugins add behaviour: filters over your content, extra tags in the page head, editor blocks, new content types, webhook subscriptions. Simple ones are a single JSON file you install from the admin with no restart.
• Themes change the look, from colours and fonts up to replacing whole page templates.

Storing your data

Start on a plain JSON file — easy to read, easy to back up, and fine for a normal site. Move to SQLite or libSQL when you want durability across restarts or more than one server, by changing one setting. Your content comes with you.

Honest limits

AstroBaaS is pre-alpha. CHANGELOG.md says what works, and TRUTH_PLAN.md measures every claim on the home page against the running code — including the ones that do not hold up yet. If something here does not match what you see, that second document is the one that is right.