Seryvon roadmap and implementation status
The Seryvon open-core release v1.0.0rc4 is now publicly tagged in the official repository. The managed product is coming soon. This page separates source-level capabilities from service availability so you can evaluate the project without treating a roadmap item as a delivery promise.
Implemented in the public source
The audit pipeline includes discovery, crawling, signal extraction and five-pillar scoring. The command-line interface exposes audit workflows, while the FastAPI application and React interface provide a local application surface. Docker Compose defines database, Redis, migration, API, web and worker services.
The source also contains provider connectors, stored-key encryption, measurement profiles, report history, artifact-store adapters and scorecard comparison. Their presence is evidence of implementation, not a statement that a managed environment is operating or that every integration has been validated with your account.
Available when configured
- External measurements: selected services require valid provider credentials and successful requests. Missing data must remain visible in coverage.
- Persistent raw artifacts: the S3-compatible backend requires an endpoint and bucket. Without that setup, the factory selects in-memory storage.
- Stored provider keys: the key-management workflow requires its encryption key. API access control is a separate setting.
- Browser rendering: the optional Playwright path requires a browser-capable runtime and explicit configuration.
- Comparisons: useful score deltas depend on compatible measurement profiles or a supported common-criteria comparison.
Managed product: coming soon
Managed hosting, continuous monitoring and collaboration belong to the operated offering described by the project. A public launch date, service-level commitment and complete commercial feature matrix are not announced on this page. Expressing interest does not create an active subscription or guarantee access to a particular feature.
For early-access discussions, explain the sites you manage, expected audit volume and the workflow you need. This provides a more useful evaluation brief than a request for a score alone. Use the early-access contact section to start that conversation.
How to evaluate progress
Check the development evidence guide before upgrading a deployment. Record a commit or release, review configuration changes, back up persisted data and compare a known audit with the previous version. A source change and a validated production release are different milestones.
Current implementation references: application services, artifact-store selection and scorecard comparison. For evaluation details, read features and the quickstart.