01
Opt in, explicitly
A codebase joins only when deliberately set as shareable. Nothing is shared automatically. You stay in control of your project.
02
Share end to end
Not just a snippet: the architectural decision and the real implementation, with code.
03
Reuse in your next task
Need SSO, payments, document generation? Check the marketplace first. Start from a working reference, not a blank page.
The catalog
Complete, production-proven solutions.
What a shared solution contains
✓Architecture decision
✓Reference files
✓Abilities & domains it covers
✓The team / source
Control & privacy. Client code stays private by default; sharing is per-codebase and reversible.
SSO & SAML login
Shared
Full identity flow — provider config, session handling, tests.
authsecurity ↻ 4
Subscription billing engine
Shared
Plans, webhooks, dunning — architecture and code.
payments ↻ 7
Document generation
Shared
Templated PDFs from structured data, cloud export.
docs ↻ 3
Event pipeline
Shared
Kafka ingestion, retries, dead-letter handling.
data ↻ 2
Feature flags
Shared
Runtime toggles with audit and rollout rules.
platform ↻ 5
Audit logging
Shared
Tamper-evident logs mapped to compliance controls.
securitycompliance ↻ 6