Project status

import { Aside, Card, CardGrid } from ‘@astrojs/starlight/components’;

PulsusDB is in active development. The repository contains substantial implementation, tests, schemas, deployment assets, and API contracts, but it is not yet presented as production-ready.

Do not build an availability-critical platform on PulsusDB yet. API, schema, configuration, packaging, and compatibility behavior may change before a stable release.

What exists in the repository

Signal parsers, query-language front ends, configuration, schema tooling, server components, and compatibility tests. Purpose-built log, metric, trace, and profile tables with distributed layouts and documented read paths. Compose fixtures, a Helm chart, native package definitions, CI workflows, and operational contracts. Golden tests, upstream corpora, differential ledgers, benchmarks, and documented intentional divergences.

Current caveats

• The public application README still warns that releases and runnable packaging are not complete.
• The application container may not be available from the documented registry yet.
• The schema script rebuilds the database instead of applying online migrations.
• Bundled ClickHouse is for evaluation, not hardened HA.
• Several feature areas are delivered milestone by milestone and may have documented gaps.
• The production-readiness checklist is not complete.

How to evaluate progress

Use these sources in order:

1. Open and closed GitHub issues for implementation state.
2. The repository’s docs/features.md for the intended capability matrix.
3. docs/production-readiness.md for operational evidence and known gaps.
4. Source and tests for the current behavior of a specific endpoint.
5. This site for task-oriented guidance and the stable conceptual model.

License

PulsusDB is released under the GNU Affero General Public License v3.0.