Polynovea's open-source work lives here as a separate portfolio from our domain products. The first project is the release-complete Content Operations Platform: a self-hostable headless CMS and structured-content operating system whose source is now public.
Polynovea Open Source · Public repository · Updated September 23, 2026
This directory is the canonical home for Polynovea's OSS portfolio. New open-source projects will be added here when they are ready rather than being mixed into the domain-product directory.
Open-source headless CMS · Structured content · Self-hosted software
An open-source, self-hostable headless CMS and structured-content platform for teams that need more than a place to type and publish pages. It brings structured data, visual schema modelling, editorial collaboration, review, releases, delivery operations, developer APIs and governed extensions into one operating surface.
Visual schema and database modelling for structured records, content-enabled models and publishable content.
Collaboration, validation, approvals, preview, release management, routes, delivery operations and observable publishing workflows.
Developer-facing contracts and automation surfaces designed to remain bounded by the same governance model as the visual product.
Open source is not a decorative distribution label. The released product is designed around ownership, inspectability, a supported self-hosted path and clear infrastructure boundaries.
The open-source path is designed so users can run the software on supported infrastructure without depending on a private Polynovea service to keep the core product useful.
The platform is built around PostgreSQL semantics and provider boundaries rather than one mandatory hosting stack. Polynovea's own deployment should be a reference, not a lock-in mechanism.
Visual workflows should not hide canonical schemas, migrations, contracts, operational plans or evidence from the people responsible for the system.
Permissions, approvals, audit, versioning and evidence belong in the normal operating path instead of being treated as optional wrappers around automation or AI.
The open-source edition is available now as the core self-hosted distribution path. MellowBase is the planned managed cloud service for teams that prefer Polynovea to operate the infrastructure; it does not replace self-hosting.
Run the platform on supported infrastructure, retain control of deployment and data, and use the public developer interfaces without depending on a private Polynovea runtime.
The planned managed cloud service built on the same OSS foundation, intended to remove operational overhead while preserving a clear self-hosted path. For HBIF, MellowBase is also intended to provide a broad cross-context observation environment for Layer 3 research where an organisation separately and explicitly permits research participation. Ordinary tenancy does not automatically feed HBIF.
No. Domain products live under Products. The Content Operations Platform belongs to Polynovea's separate open-source portfolio and has a different distribution and product role.
Yes. The defined self-hosted OSS release scope is complete and the source is public at github.com/Polynovea/OSS1. The historical repository tag should not be used as a substitute for the current release-completeness state.
Yes. The planned managed version is called MellowBase. Its product role is managed Content Operations; its HBIF research role is to provide a broad cross-context observation environment for Layer 3 experiments where separate research permissions exist. It does not remove the public self-hosted OSS option.