Open-source tools for faster, more stable Docyrus development.
Client SDKs, auth helpers, UI primitives, and MCP tooling published openly so teams can adopt the stack, inspect the implementation, and ship without black-box dependencies.
Public by default: package versions, source, issue flow, roadmap signals, and release notes.
Closed developer tooling creates avoidable risk.
The main value of the open-source stack is simple: fewer hidden decisions between install and production.
Vendor Lock-in
Proprietary APIs are hard to audit, fork, or migrate away from.
Hidden Dependencies
Opaque SDK behavior creates debugging dead ends when things break.
Slow Updates
Closed libraries can block teams for weeks while they wait for fixes.
No Community Input
Roadmaps controlled by one vendor rarely match what integrators need most.
Trust Gaps
Security and implementation decisions stay hidden until they fail in production.
Dead Ends
Closed ecosystems disappear when the vendor changes direction.
Everything you need, publicly available
The package surface is intentionally small: adopt the layer you need, then add the next one when the integration gets deeper.
Typed REST access to Docyrus data source endpoints.
OAuth2 helpers for PKCE, iframe, client credentials, and device code.
Reusable components for Docyrus-style product surfaces.
MCP foundations for tools that connect to Docyrus tenants and APIs.
Shape the ecosystem you build on
Open-source is part of the product surface, so contribution paths should be obvious and low-friction.
Open issues make bugs, demand, and workarounds visible.
Pull requests are reviewable and credited in release notes.
Roadmap signals help teams plan before they commit to an integration.
From install to production in hours
The shortest useful story is the one that matters: install the packages, generate types from your schema, then ship on a stack you can still inspect.
Install
Add the packages you need from npm and keep adoption incremental.
Generate
Use your live schema to keep types aligned with what your tenant exposes.
Ship
Combine SDKs, UI primitives, and MCP tooling without reverse-engineering the stack.
Frequently asked questions about Open Source
What is Open Source?+
Open Source is the public Docyrus collection of SDKs, auth helpers, MCP tools, and UI libraries released in the open.
When should developers use Open Source?+
Developers should use it when they want installable packages, reference implementations, and GitHub-based workflows for building on Docyrus.
What can teams ship with Open Source?+
Teams can ship integrations, client apps, auth flows, and reusable front-end or tooling packages faster with maintained libraries.
How does Open Source fit with other Docyrus developer tools?+
It complements the API, Agent Skills, and MCP tools by giving developers code-level building blocks for the Docyrus stack.