This release is a pre-release and may not be stable for production use.
sandloom-billing
The Sandloom billing module: plans, subscriptions, the credits ledger and the
Stripe integration (with a fake PSP default). Import package
sandloom_billing; it registers the sandloom.modules entry point
billing = "sandloom_billing", so its module name is billing (tables
billing_*, migration chain alembic_version_billing, channels and contracts
billing.*). Depends on sandloom>=0.7.0a1,<0.8; on no other module.
pip install "sandloom[redis,celery]==0.7.0a1" sandloom-billing==0.7.0a1
sandloom.main:app composes it once installed; an app selects it with
SANDLOOM_MODULES=billing (or sandloom new <app> --with billing). Other
modules call it through its contracts; their DTOs, stubs and event schemas
live in sandloom.shared and ship with sandloom.
Source of truth lives in the monorepo at src/sandloom_billing; this package
builds the wheel and source archive.
Project links
Source · Documentation · Changelog
This is the initial 0.7.0a1 alpha distribution. The canonical source
repository is private and awaiting transfer; the documentation website is
not deployed yet. The project links above are the planned public locations.
License
Apache-2.0. Copyright 2026 Vasyl Cherniavskyi. See LICENSE and NOTICE.
Metadata
Release files for sandloom-billing 0.7.0a1
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 | Actions |
|---|---|---|---|---|
| sandloom_billing-0.7.0a1.tar.gz | 90.4 kB | Without provenance | Details for sandloom_billing-0.7.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sandloom_billing-0.7.0a1-py3-none-any.whl | Python 3 | none | any | Details for sandloom_billing-0.7.0a1-py3-none-any.whl |
Total release size: 208.5 kB
Release files / sandloom_billing-0.7.0a1.tar.gz
| Download URL | sandloom_billing-0.7.0a1.tar.gz |
|---|---|
| Size | 90.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d422c0087ea0d387e2d1d38513809f56cb4363d3f223dad2f2288738d0d8da19
|
|
BLAKE2b-256 checksum How to use checksums |
6eca51356bc515b43595cec08864c92de53e6dfe7092d8e9c84611056abf9ecc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / sandloom_billing-0.7.0a1-py3-none-any.whl
| Download URL | sandloom_billing-0.7.0a1-py3-none-any.whl |
|---|---|
| Size | 118.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21bfacb0317af6b9ed949683474f84fbc5e55a1177c1ec0cde939a80d090b48b
|
|
BLAKE2b-256 checksum How to use checksums |
0d0c2d05c2ab6f21697eca564fdcf65b700e1784ad8f12afefa4f2f7b86ea399
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for sandloom-billing 0.7.0a1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.