This release is a pre-release and may not be stable for production use.
Sandloom
Python backend framework for AI-driven development.
Build with people and AI agents while the framework enforces module boundaries, owns transactions and provides shared mechanisms for authorization, tenancy, event delivery and idempotency.
Why Sandloom
- AI-driven development: a consistent module structure, typed contracts, CLI scaffolding, agent instructions and executable quality gates keep changes scoped as the application grows.
- Enforced module boundaries: business modules communicate through typed events and contracts. Architecture checks reject cross-module imports.
- Pluggable infrastructure: application modules use capability contracts instead of raw backend clients. Configure compatible registered drivers or implement adapters without spreading infrastructure SDKs through business code. PostgreSQL and Redis are the documented production backends.
- Monolith to services: deploy the same business modules together or in separate services using module selection and service bindings. Moving existing data to a module's own database is a separate offline extraction step.
- Built-in mechanisms: transaction ownership, one writer per request, authorization rechecks before commit, tenant isolation, a transactional outbox, durable consumers and idempotent commands.
Install and create an application
Requires Python 3.11+, uv and Docker for local
PostgreSQL and Redis services. Sandloom is an alpha; --pre allows pip to select
its prerelease packages.
python -m pip install --pre "sandloom[standard]"
sandloom new myapp --with identity,tenancy,billing --module notes
Follow the printed next steps to install application dependencies, start local services, run checks and migrations, and launch the API.
The standard extra includes Redis, Celery and the separate sandloom-identity,
sandloom-tenancy and sandloom-billing packages. Install sandloom alone for
the kernel, public sandloom.sdk, shared contracts, CLI and composition root.
Other extras: redis, celery, fast, check, testing and sentry.
Inspect before editing
From the application root, after installing its dependencies:
uv run sandloom generate
uv run sandloom graph
uv run sandloom context notes
uv run sandloom explore
graph shows module purposes and declared connections; context gives a compact
map of one module's contracts, events and owned files. Both default to text;
request JSON explicitly with --format json. explore opens an offline browser
view with declared processes, interface impact and architecture comparisons.
See module maps and the
architecture explorer.
Alpha status
Sandloom is under active development. Review the compatibility policy and release
notes before upgrading; a minor version in the 0.x series may introduce
breaking changes. The framework's documented guarantees have specific scopes;
consult the guarantee reference for their mechanisms and limits.
Links
License
Apache-2.0. Copyright 2026 Vasyl Cherniavskyi. See LICENSE and NOTICE.
Metadata
Release files for sandloom 0.7.0a4
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-0.7.0a4.tar.gz | 1.3 MB | With provenance | Details for sandloom-0.7.0a4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sandloom-0.7.0a4-py3-none-any.whl | Python 3 | none | any | Details for sandloom-0.7.0a4-py3-none-any.whl |
Total release size: 2.9 MB
Release files / sandloom-0.7.0a4.tar.gz
| Download URL | sandloom-0.7.0a4.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd960de94ad4566ad86014bc40e4afa5e94392c64ff94e442569bd7f9e75bbca
|
|
BLAKE2b-256 checksum How to use checksums |
4ff2ba1d0ecaa2e14df21d3c2b7f50864c756b58a19e4e7ee4e15d4efedd7652
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 31, 2026.
Transparency logRelease files / sandloom-0.7.0a4-py3-none-any.whl
| Download URL | sandloom-0.7.0a4-py3-none-any.whl |
|---|---|
| Size | 1.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
794b1884f8ec98e44ad9a503e11e020efd9e4f62e86fc6690af40dfd4700ffc3
|
|
BLAKE2b-256 checksum How to use checksums |
8bc524ed3371950d2f4fd16c6dc995523e2ca03ba16d96811a9d21f8b22b9ed0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 31, 2026.
Transparency logSecurity for sandloom 0.7.0a4
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 sandloom-0.7.0a4.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 Oct 31, 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.