The ecosystem

Built to be
built on.

Pyxle plugins are one config line: declare them in pyxle.config.json and they wire themselves at startup. Two official plugins ship today — and five founding slots in this directory are reserved for the community.

01 — Official

The plugins Pyxle ships.

Built and maintained by the core team, held to the same standards we ask of everyone — tested against real PostgreSQL and MySQL servers in CI, fail-secure by default, honest about scope.

pyxle-db

Databases

One explicit-SQL API over SQLite, PostgreSQL, and MySQL — portable placeholders, a uniform Row, checksum-tracked migrations, and the DatabaseLike contract other plugins build on.

pip install pyxle-db
DocsPyPISource

pyxle-auth

Authentication

Email + password accounts on argon2id — sliding sessions, password-reset and verification flows, wildcard RBAC, scoped API tokens, and request guards. Fail-secure by default.

pip install pyxle-auth
DocsPyPISource

As the ecosystem grows, this directory organises by what you're trying to do — Mail, Storage, Caching, Background Jobs — with a recommended pick and the alternatives in each. The aim isn't the most plugins; it's one obvious way to do most things, with room to choose differently.

02 — The founding cohort

Be one of the first five.

A launch program, not a permanent club: the first 5 community plugins to meet the published standards are recognised as ecosystem pioneers — and get the spotlight, review, and roadmap seat below while they build. All five spots are open. After the cohort, the directory stays open to everyone, organised by capability.

Pioneer recognition
A permanent place among the plugins that started the ecosystem — recognition that grows in value as Pyxle does, not a gate on anyone after you
The spotlight
A featured slot on this page and a launch write-up from the official account
The review
Direct code review and pairing from the core team while you build
The seat
Co-design input on Phase B — the plugin pages & routes API — before it ships
Founding slot 01

Reserved. Could be yours.

Founding slot 02

Reserved. Could be yours.

Founding slot 03

Reserved. Could be yours.

Founding slot 04

Reserved. Could be yours.

Founding slot 05

Reserved. Could be yours.

Ship under your own package name — the bare pyxle-* namespace is reserved for official plugins, and a cohort plugin may be granted its canonical name. Community plugins are listed under their author's name and are not security-audited by the Pyxle team. The bar is public; reviews are honest.

03 — Build one

Three steps to a founding slot.

Today plugins contribute services and middleware — database layers, mailers, storage, observability. Pages and routes are next: the Phase B RFC is open, and founding authors help design it.

  1. 01

    Pick a quest

    The ideas page lists plugins the ecosystem needs, scoped to what the plugin API supports today — each with the contract it builds against and an honest size estimate.

    Browse plugin ideas →
  2. 02

    Clear the bar

    The standards are published and finite: packaging, behaviour, testing, security, maintenance. The official plugins are the reference implementation of every rule.

    Read the standards →
  3. 03

    Submit it

    Open a submission issue — early is better, so the slot is visibly claimed and review can happen while you build instead of after.

    Open a submission →
Claim a founding slotRead the Phase B RFC