The ecosystem

Built to be
built on.

A plugin is one line of config. Declare it, and it wires itself at startup — a request-scoped database, session middleware, a mailer. Three ship today; five founding slots are open to the community.

pyxle.config.jsondeclare · wired
{
  "plugins": [
    "pyxle-db",
    "pyxle-auth",
    "pyxle-mail"
  ]
}
Each line turns a service on at startup — no glue code between the config and the request.

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

Database for Pyxle over SQLite, PostgreSQL, and MySQL — an explicit-SQL API or an optional SQLAlchemy ORM, both with request-scoped injection, automatic transactions, and a migration CLI (checksum migrator or Alembic).

  • database
  • sqlite
  • postgresql
  • mysql
  • orm
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.

  • auth
  • sessions
  • rbac
  • tokens
pip install pyxle-auth
DocsPyPISource

pyxle-mail

Mail

Transactional email over a swappable MailProvider contract — console, SMTP, and Resend providers, sender defaults, and fail-loud config. The mailer pyxle-auth's reset and verification flows hand their tokens to.

  • mail
  • email
  • smtp
  • resend
  • transactional
pip install pyxle-mail
DocsPyPISource

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 — pyxle-* is reserved for official plugins. Community plugins aren't security-audited by the Pyxle team; the bar is public and 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