The workspace that keeps up with engineers
Knowledge base, reviews, and observability in one place. Clean, intuitive, and reliable.
Bring engineering context together
Write, review, and use internal engineering docs with code and observability alongside the text.
Architecture decisions, API specs, runbooks, and incident procedures deserve a pull-request-style workflow. Propose edits, request review, and keep a clear history.
Make complex information easy to follow and hard to misread.
Attach freshness hooks to a block or page. When sources change, they flag what is stale.
Live system metrics belong inside your knowledge base. Document what each metric means, why the thresholds exist, and what changed, without jumping between tools.
The technical knowledge base
Easy to write. Even easier to read. Document endpoints, parameters, examples, and edge cases in polished, structured blocks that feel native and stay easy to navigate.
Your docs have dependencies, too
API docs depend on code. Runbooks depend on container image versions. Observability depends on both. Track those dependencies inside your knowledge base with freshness hooks.
Observability + knowledge base
Put the graph next to the explanation. Document what each metric means and what "good" or "bad" looks like, with the live chart right there on the page.
Familiar review process
API spec updates, RFCs, postmortems, and observability config changes deserve a real review flow. Git workflows fall apart on long-form, formatted writing. Oxynote keeps the same review principles, with a rich-text editor.
Frequently Asked Questions
Oxynote is an internal knowledge base for engineers, from solo builders to full tech orgs. It works best for engineering and infra teams who need architecture decisions, operational decisions, runbooks, procedures, and observability dashboards with clear context.
Oxynote is built specifically for engineering workflows. It focuses on decision and operational content, connects to developer tooling, and reduces context switching by bringing writing and live metrics together.
Anything your engineering org needs to write down and reuse. Oxynote is a general-purpose internal knowledge base, but it shines for architecture decisions, RFCs, design docs, runbooks, procedures, postmortems, and metric dashboards that need clear context.
Early access is free. We open new accounts in batches as slots become available, and we also invite people directly. If sign-ups are closed right now, join the waitlist and we’ll reach out when the next batch opens.
Optionally, Oxynote can connect to external sources so your internal pages stay tied to what they reference. That includes GitHub for code changes, Prometheus for live metrics, Slack for team context, Docker image registries for new releases, and any third-party URL you attach to track website content changes.
No. Oxynote is for internal engineering information, more like a private workspace than a public docs site. It’s built for teams to keep architecture decisions, runbooks, procedures, and operational context organized and accessible to the right people.