Run it
Shio is a Spring Boot 4 / Java 21 application you run yourself. Start it as a
container or a JAR, point it at PostgreSQL, MariaDB/MySQL or the bundled H2, and the
schema is migrated for you: Liquibase owns it, so an upgrade is a restart, not a
hand-written ALTER. Nothing calls out to a hosted service: Shio holds no model and
no prompts, so the content, the files and the keys stay on your infrastructure.
From there it is configuration and access. One JVM can serve many isolated tenants, each with its own content, users and quota. Authentication covers session login for the console, OAuth2/OIDC, and API keys for everything headless, with CSRF, CORS and the HTTP firewall configured out of the box. Full-text search works with no extra infrastructure, and indexing into Viglet Turing ES is available when you want faceted enterprise search, opt-in, reached when content is published.
Installation Guide
Viglet Shio CMS Installation Guide: Docker, JAR, build from source, database setup, and Linux service.
Configuration Reference
Every Viglet Shio configuration property, read from the tree: the instance, the delivery API, the agent surface, files and images, Turing indexing, and the schema.
Multi-Tenancy
Run one Viglet Shio instance that serves many isolated tenants: discriminator-based data isolation, provisioning, membership, plan quotas and suspension.
Search & Caching
Full-text search in Shio, the opt-in Viglet Turing ES indexing that makes content searchable on publish, and the caching layers between a request and the database.
Security
Authentication in Viglet Shio: sessions for the console, API-key scopes for everything else, what an AGENT key may not do, CSRF on cookie callers only, and CORS.