The Fibric community.
The public Fibric builder community is not open yet. The connector and operator model is documented as a reference preview while the CLI, SDK packages, public API, and contribution workflow are prepared.
Three honest ways in.
There is no public Discord, discussion board, SDK repository, or contribution program to join today. These are the channels that actually exist.
Reference docs
Read the proposed platform contract, connector shape, governance model, and API surface. The pages are a preview, not an executable public SDK.
fibric.io/docsTalk to the team
If you have a real integration or operating problem, describe the system, the action boundary, and what evidence you need. We will tell you what is live and what is not.
fibric.io/company#contactManaged early access
Request a deployment review for a connector, operator, or product pattern. Early access is collaborative and provisioned by the Fibric team.
fibric.io/onboardingThings you can inspect today.
The marketplace exposes real maturity states. The docs and release notes show the intended developer surface, clearly marked as reference preview.
-
01 · Browse The connector directoryMarketplace →
Forty-eight certified listings in one place: five live in BearScope and forty-three delivered through managed early access. Each listing states its maturity and action boundary.
-
02 · Learn GuidesRead the guides →
Reference walkthroughs for the proposed CLI, SDK, and API surface. They are useful for design review but are not runnable public setup instructions today.
-
03 · Track Release previewSee what's new →
A clearly labelled roadmap of the developer surface being prepared. It no longer represents packages or releases that have not actually shipped.
Review the connector contract.
The docs describe an MCP-shaped connector contract and the governance the generalized runtime is intended to provide. The public SDK and publishing path are not available yet.
-
Review the proposed SDK shape
defineConnector, tool, and auth describe the intended contract. They are design references, not proof of downloadable packages, a public build workflow, or deployment readiness.
-
Let governance do its job
The reference design separates proposal, policy, and execution. Single-flight and idempotency keys are intended to reduce duplicate effects; a real connector must still be validated against its downstream system.
-
Prepare for managed review
A public publishing workflow is not open today. Early-access connectors are reviewed and provisioned with the Fibric team, including their permissions, duplicate-handling behavior, and recovery limits.
Where the community shows its work.
Two places to come up for air: the things we do live, and the things people have built that are worth a closer look.
The current way in is a managed review.
Bring a real system and a bounded operating problem. We will tell you whether it maps to a live BearScope capability, managed early access, or a reference pattern.