PyVELM
Odoo's semantics. Laravel's ergonomics. Filament's craft — in a Tailwind-native ERP shell that exists only here.
PyVELM is a declarative Python ERP on SQLAlchemy-backed databases (PostgreSQL, SQLite, MySQL/MariaDB, SQL Server, Oracle, and other supported dialects): recordsets and modules in the Odoo tradition, developer and admin patterns borrowed from Laravel and Filament, and a bespoke Tailwind v4 + HTMX interface—its own layout, widgets, and look & feel—not Odoo's web client or Filament's Blade stack.
Backend matrix and DSN examples: docs/multi-database.md.
Latest: v1.4.6 — Filament-style schema field reactivity on forms. See the docs (version picker for older releases).
Full documentation: coolsam726.github.io/pyvelm
The framework is PyVELM; the PyPI package
and CLI stay pyvelm (lowercase).
Install
pip install pyvelm==1.4.6
Greenfield app:
pipx install pyvelm
pyvelm init my_erp
Hack on the repo
git clone https://github.com/coolsam726/pyvelm.git
cd pyvelm
python3 -m venv .venv && .venv/bin/pip install -e .
cp .env.example .env # set PYVELM_DSN
.venv/bin/python examples/basic.py
Contributing, tests (pip install -e ".[test]" && pytest), local docs (mkdocs serve),
and releases: CONTRIBUTING.md.
Maintainer notes: CHANGELOG.md · CONTEXT.md.
Sponsor
Open-source business-app tooling maintained by Sam Maosa. Sponsor on GitHub supports all of these projects—not just PyVELM.
| Project | |
|---|---|
| This repo | PyVELM — declarative Python ERP |
| 1 | filament-modules — Filament + nWidart/laravel-modules |
| 2 | flatpickr — Flatpickr date picking for Filament |
| 3 | nested-comments — nested comments on Filament forms & pages |
| 4 | typeorm-pagination — pagination for Express + TypeORM |
| 5 | filament-signature-pad — signature field for Filament forms |
Same craft across stacks: admin UX that feels intentional, released in the open with docs and tests. If any of this saves you a sprint, sponsorship keeps it sustainable.
License
LGPL-3.0-or-later — Copyright (c) 2026 Sam Maosa.
If you link against or modify PyVELM, see the license file for your obligations
(shared library / combined work terms).
1 maintainer
Metadata
1 maintainer
Release files for pyvelm 1.4.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyvelm-1.4.6.tar.gz | 1.5 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyvelm-1.4.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 MB
Release files / pyvelm-1.4.6.tar.gz
| Download URL | pyvelm-1.4.6.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4b45da946160c7487d1767e4a4fcf39e9c478c4112b72684527d6c1127dc8bb
|
|
BLAKE2b-256 checksum How to use checksums |
6cf970758e3159a6a7231028dd4d8ff18e3cdfaf9d213c8c28534a952ee1514f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 12, 2026.
Transparency logRelease files / pyvelm-1.4.6-py3-none-any.whl
| Download URL | pyvelm-1.4.6-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e4bba3fb8ab1bf22071820b13d03aa84ab5a58edf238dbf8daeeed00da10dae9
|
|
BLAKE2b-256 checksum How to use checksums |
eccf6776b023d24ea67d79addbb6c5f5f1e573701d82ab98913e0918aa79dd2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 12, 2026.
Transparency log
