⚡ Larz
New in 2.1 — Scaffolder —
larz new <name> --template api|saas|ai|marketplacegenerates a complete, runnable project. Plus real-world examples (URL shortener, link-in-bio) and honest benchmarks.
New in 2.0 — Async + Postgres — an ASGI/async core with WebSockets (and a built-in zero-dependency async server, no uvicorn needed) plus a pure-Python PostgreSQL driver with SCRAM-SHA-256 auth. Still zero dependencies; sqlite stays the default.
New in 1.3 — Modern API — typed request binding & validation from function signatures, dataclass bodies, dependency injection (
Depends), Server-Sent Events, CORS and lifecycle hooks. FastAPI-style ergonomics, still zero dependencies.
New in 1.2 — the Revenue Engine — pricing-as-code, revenue analytics (MRR/ARR/churn/LTV), dunning & recovery, referrals/affiliates, and AI monetization (token metering with BYOK). Larz is now revenue-native and AI-native. See the changelog.
New in 1.1 — TOTP 2FA, social login (Google/GitHub), file uploads, a marketplace payout ledger, four more payment providers (Square, Razorpay, Mollie, Coinbase Commerce), and a first-class test client. See the changelog.
![]()
![]()
![]()
The money-native web framework.
pip install larz
Larz is a small, from-scratch, dependency-free Python web framework where payments, paywalls, subscriptions, trials, and usage-metering are first-class primitives — not something you bolt on with three libraries and a weekend.
Flask makes routes easy. Django makes data easy. Larz makes getting paid easy.
from larz import Larz
import larz.money as money
app = Larz(secret="change-me")
money.enable(app) # payments on. Zero keys in dev.
@app.paid("$9/mo", trial_days=7) # subscription with a free trial
@app.get("/pro/report")
def report(req):
return "<h1>Pro report for %s</h1>" % req.subject
@app.metered("$0.02/call") # per-call billing from prepaid credit
@app.post("/api/summarize")
def summarize(req):
return {"summary": run(req.json()["text"])}
app.run()
A request to /pro/report from someone who hasn't paid is automatically
sent through checkout (or given their free trial); when they come back, they're
served. A request to /api/summarize with no credit gets a clean 402. You
never write if user.is_paid.
Batteries included — all pure stdlib
| Area | What you get |
|---|---|
| Money | @app.paid · @app.metered · @app.plan · subscriptions, renewals, cancel + dunning · free trials · coupons · credit packs · invoices/receipts · customer portal (/larz/account) · entitlement events · /larz/admin revenue dashboard |
| Providers | Mock · Stripe · Paddle · Lemon Squeezy · Paystack · PayPal · GemVault · Dodo · Crypto — all via stdlib urllib, no SDKs. Add your own in ~40 lines. |
| Auth | larz.auth — users, scrypt passwords, @app.login_required, req.user, API keys (@app.api_key_required, plan-gated), RBAC (@app.require_role), email-verify + password-reset tokens |
| API tooling | @app.validate(schema) · auto OpenAPI (/openapi.json + /docs) · paginate() · a webhooks framework (sign, deliver, retry) |
| ORM | larz.models — relationships (ForeignKey), field types (datetime/json/decimal…), query operators (views__gt, title__like), pagination, hooks, transactions, auto-migrations |
| Admin | larz.admin — an auto-generated CRUD admin panel over your models |
| Ops | larz.ops — @app.cache · background jobs (@app.job) · cron scheduler (@app.schedule) · email (SMTP) · .env config · /healthz + /metrics |
| Templating | {{ }} / {% for %} / {% if %} · inheritance ({% extends %}/{% block %}) · filters (` |
| Core | WSGI engine · typed routing · signed-cookie sessions · blueprints · static files · debug pages |
| Security · SEO · CLI | Rate limiting, bot filter, CSRF, CORS · auto sitemap/robots + OpenGraph + IndexNow · larz new / run / routes |
Why
Every other framework treats money as an afterthought — the thing you wire up last, badly, copy-pasted from a payments tutorial. But for indie hackers, solopreneurs, and anyone shipping a product to make a living, monetization isn't the afterthought — it's the point. Larz puts it in the core.
Use it for
- Paid / metered APIs — AI wrappers, data APIs (
@app.meteredper call) - Content paywalls — reports, courses, paid newsletters (
@app.paid) - Digital products — one-off unlocks and downloads
- Micro-SaaS — a free tier + a Pro plan with a trial (
@app.plan)
Design principles
- Zero dependencies. Pure Python standard library —
sqlite3,urllib,wsgiref. Runs anywherepython3runs, including constrained boxes and phones. - Provider-agnostic. The framework never hard-codes a processor. Implement
create_checkout+parse_webhookand any processor drops in. - Portable by default. No modern-SQLite assumptions, no C extensions.
Run the demos (no API keys)
python3 examples/paid_app.py # the essentials: paid + metered routes
python3 examples/saas_app.py # a full mini-SaaS: plans, trials, credits,
# templates, ORM, dashboard, security
Then open http://127.0.0.1:8000/ and click through. Visit /larz/admin?token=admin123
on the SaaS demo to see the revenue dashboard.
Test
python3 tests/test_core.py # 15 — routing, sessions, paywall, metering
python3 tests/test_features.py # 43 — money, providers, templating, security
python3 tests/test_v1.py # 52 — ORM, auth, API, admin, ops, billing
110 checks, no pytest required.
Scaffold a new app
python3 -m larz new myapp
cd myapp && python3 -m larz run
Status
v1.0.0 — real and tested, but not yet production-hardened (WSGI dev server, in-memory rate limiting, MockProvider is dev-only). Roadmap: ASGI/async core, production server recipe, dunning/renewal reminders, richer analytics, a hosted docs site at larzos.com/larz.
Runs on your infrastructure, not ours
Larz is a library you pip install — it has zero runtime dependencies and makes no calls to any Larz/vendor server. Everything (payments via the keyless mock provider, auth, the ORM, 2FA, uploads, pricing, revenue analytics, AI metering) runs entirely on your machine, offline. The only network calls Larz ever makes are to services you configure with your keys — Stripe/Paddle/etc. for real payments, Google/GitHub for social login, your LLM provider for AI. Your data and your customers stay in your database, on your server. There is no telemetry and no phone-home.
License
MIT.
Metadata
Release files for larz 2.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| larz-2.2.1.tar.gz | 102.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| larz-2.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 192.2 kB
Release files / larz-2.2.1.tar.gz
| Download URL | larz-2.2.1.tar.gz |
|---|---|
| Size | 102.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7d4027f9e0a0a80c0b3b57d71caa2f52b4abfca0e380fe9548eacf0eaa97e50
|
|
BLAKE2b-256 checksum How to use checksums |
96229992627fb8abd80c245f1a2fa73e686d209650cfdf4e1bb1450783ba6f26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 26, 2026.
Transparency logRelease files / larz-2.2.1-py3-none-any.whl
| Download URL | larz-2.2.1-py3-none-any.whl |
|---|---|
| Size | 89.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d2834e7cfb5eae06ac00ac824b8f468e84ea305e366bd09e3912df41952892e
|
|
BLAKE2b-256 checksum How to use checksums |
8c32e73c4982331009e10ded11ad87b32f947debf2eb8ad373869a489575eda3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 26, 2026.
Transparency logSecurity for larz 2.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for larz-2.2.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.