Nido · first product
KitaNido
KitaNido is the first product built on the WebPlatform and is currently being piloted with organisations. The public state at kitanido.ashacore.de serves as the Prism demonstrator.
Project · WebPlatform
A website for your organisation—from a shared, tested core, not as an individual software project. Operated in Germany.
Product families
Nido and Sede are developed on the AshaCore WebPlatform. Shared content, permissions and operations meet suitable page structures and an individual design.
Nido · first product
KitaNido is the first product built on the WebPlatform and is currently being piloted with organisations. The public state at kitanido.ashacore.de serves as the Prism demonstrator.
Nido · planned
For schools and school networks: school profile, everyday life, news and essential information in a suitable structure · status: planned.
Nido · planned
For clubs and associations: activities, sections, events and contacts on a maintainable website · status: planned.
Sede · first pilot
Leovino is the first Sede pilot for professional organisations and tests an individual brand world on the shared core.
Packages and modules
The packages describe how organisations can use the WebPlatform. Each building block carries its current status.
in pilot phase
Managed content care by us.
in pilot phase
Your own content editing through the editorial interface.
in progress
Your own colour and type world within tested boundaries.
in progress
Tested accessibility as the standard.
planned
Protected area for parents, members and clients · separate security approval required.
planned
Several sites of one organisation or network in one account.
Hosting and privacy
The platform is operated at Hetzner in Germany. Data processing, data minimisation, defined access and traceable data flows are part of the design.
Location
Hetzner Germany is the hosting foundation and a data processing agreement exists. The services actually used are stated for each scope.
Minimisation
The platform core uses local resources and no third-party CDNs. Unnecessary third-party requests are avoided.
Boundary
No certifications are stated. Privacy and security evidence applies to the scope that was actually tested.
Security
Security comes from architectural boundaries, tests, reviews and traceable releases. The customer statement is deliberately narrower than a blanket security promise.
Documented
Tenant separation and public read paths are tested; prohibited access must reliably fail.
Stated
An external pentest is planned and has not taken place. Internal tests and reviews are separate from it.
Scope
Protected portals, uploads and sensitive data increase the verification work and receive their own security approval.
For technical readers · WebPlatform structure
The Control Plane provisions a site from product, preset, organisation and content. Editorial and Design-Lab write drafts to the Control Plane; only publication crosses the boundary to the public state. Prism resolves the domain to the site and fetches configuration and published content. The UI-Kit renders the resulting appearance in the browser.
documented
Backend for accounts, organisations, sites, roles and permissions, content, publishing boundary and provisioning.
documented
Multi-tenant runtime: resolves the domain to the site and server-renders every presence from configuration, theme tokens and published content.
documented
Shared layouts, components and design tokens for all product profiles.
documented / in progress
Draft, preview, approval and publication; review, history and rollback in progress.
in progress
Blueprints and page templates versioned in the Control Plane.
planned
Upload, storage, consent and delivery of media.
planned
Operator view for overview, health, audit and provisioning.
documented / in progress
Reads existing websites and produces structured import data; preview and approval flow in progress.
in progress
Operation in Germany on Hetzner, infrastructure as code and runbooks per application.
For technical readers: RLS, negative tests and CI levels form the technical proof boundaries behind the customer-facing statement.
Three equal fields for the website product: no percentage, only the documented state of the work.
WebPlatform structure
The product page starts with packages and modules; technical depth follows for interested readers.
Product core
Tested building blocks, configuration and content form independent websites.
Tenant
Account, organisation and site form a separated, reproducible web presence.
Publishing
Draft and published state remain separate.
Documented state
These statements summarise the internally documented engineering state; they are not a public availability promise.
Practice
KitaNido is the first product built on the WebPlatform and is currently being piloted with organisations. The public state at kitanido.ashacore.de is the Prism demonstrator. Leovino is the first Sede pilot.
Hosting and privacy
Operated at Hetzner in Germany with a data processing agreement. No tracking requirement and no third-party CDNs.
Security
Tenant separation reaches into the database. No certifications are stated. An external pentest is planned and has not taken place.