Plugins · The directory

Built to be built on.

a plugin is one line of config · 3 official on PyPI · 5 of 5 founding slots open

pyxle.config.jsonwired at startup

1{2  "plugins": [3    "pyxle-db",4    "pyxle-auth",5    "pyxle-mail"6  ]7}

each line turns a service on at startup — no glue code between config and request: pyxle-db → request.state.db · pyxle-auth → session middleware · pyxle-mail → get_mail_service()

01 · Official

The plugins Pyxle ships.

3 official, on PyPI · CI against live PostgreSQL and MySQL · fail-secure by default · core-team built, same bar as everyone

pyxle-db0.3.0databases

from pyxle_db import get_database

db = get_database()
row = await db.fetchone("SELECT …")

SQLite · PostgreSQL · MySQL, one explicit-SQL API
optional SQLAlchemy ORM
request-scoped injection · automatic transactions
migration CLI — checksum migrator or Alembic

docs →pypi source/docs/plugins/pyxle-db

pyxle-auth0.4.2authentication

const { user, isAuthenticated,
        logout } = useAuth()
if (!isAuthenticated)
  return <a href="/login">Sign in</a>

email + password accounts on argon2id
sliding sessions · reset & verification flows
wildcard RBAC · scoped API tokens · request guards
fail-secure by default

docs →pypi source/docs/plugins/pyxle-auth

pyxle-mail0.1.0mail

mail = get_mail_service()

await mail.send(to=email,
    subject=subject, html=html)

swappable MailProvider contract
console · SMTP · Resend providers
sender defaults · fail-loud config
carries pyxle-auth's reset & verification tokens

docs →pypi source/docs/plugins/pyxle-mail

02 · Founding

Be one of the first five.

a launch program, not a club · 5 of 5 slots open — the ledger below is the live count

slot 01open — could be yoursunclaimed

slot 02open — could be yoursunclaimed

slot 03open — could be yoursunclaimed

slot 04open — could be yoursunclaimed

slot 05open — could be yoursunclaimed

recognitiona permanent place among the plugins that started the ecosystem

spotlighta featured slot here + a launch write-up from the official account

reviewcore-team code review and pairing while you build

seatco-design input on Phase B — plugin pages & routes — before it ships

ship under your own name — pyxle-* stays official · community plugins aren’t security-audited by the core team · after the cohort, the directory stays open to everyone

03 · Build one

Three steps to a founding slot.

services and middleware today — pages next, co-designed in the open

Pick a quest

the ideas page lists what the ecosystem needs — each with its contract and an honest size estimate

browse the ideas →

Clear the bar

published, finite standards — packaging, behaviour, testing, security, maintenance · the official plugins are the reference implementation

read the standards →

Submit early

open the submission issue while you build — the slot is visibly claimed, review happens alongside

open a submission →

read the Phase B RFC →

MIT · v0.9.4 · Python 3.10+ · pre-1.0