bedrock
bedrock is the runtime core of the Bedrock modular framework.
It provides manifest-driven module loading, lifecycle management, and first-party contrib modules for common capabilities.
Status
The core runtime is fully implemented and functional.
This package contains production-ready subsystems:
- Module registry with dependency resolution and lifecycle hooks
- Dependency injection container with singleton/transient/scoped lifetimes
- Hook system for structured call/response extension points (sync, async, robust)
- SQLAlchemy 2.0 database layer with Alembic migrations
- Cache system with memory and Redis backends
- Signal/event system (blinker-derived)
- Typer-based CLI for module and database management
- Comprehensive utility library (lazy loading, introspection, string helpers)
Installation
# With uv (recommended)
uv add bedrock-core
# With poetry
poetry add bedrock-core
# With pip
pip install bedrock-core
Quick Start
import bedrock
# Initialize the runtime (discovers and loads modules)
bedrock.setup()
# Access key singletons
from bedrock.module import apps # ModuleRegistry
from bedrock.database import db # DatabaseManager
from bedrock.contrib.cache import cache # CacheService
Key Singletons
| Singleton | Class | Import |
|---|---|---|
apps |
ModuleRegistry |
from bedrock.module import apps |
container |
Container |
from bedrock.di import container |
hooks |
HookRegistry |
from bedrock.hooks import hooks |
db |
DatabaseManager |
from bedrock.database import db |
cache |
CacheService |
from bedrock.contrib.cache import cache |
Module Structure
my_app/
├── __init__.py
├── manifest.yaml # Module identity and dependencies
├── models.py # SQLAlchemy models (optional)
├── entities.py # Pydantic models for validation
├── service.py # Business logic
├── exc.py # Module exceptions
└── bootstrap.py # Lifecycle hooks
Architecture
Bedrock is framework-agnostic by design. The core runtime has no HTTP dependencies and is usable in:
- API servers (FastAPI, Flask, etc.)
- Background workers (Celery, etc.)
- CLI tools
- Scripts and automation
For more details, see the documentation.
Metadata
Release files for bedrock-core 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bedrock_core-0.2.0.tar.gz | 74.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bedrock_core-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 178.5 kB
Release files / bedrock_core-0.2.0.tar.gz
| Download URL | bedrock_core-0.2.0.tar.gz |
|---|---|
| Size | 74.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
956b0ce55f8fea2e5f1c2ae0d5462a485b92e26a3fc972640324633fd8206646
|
|
BLAKE2b-256 checksum How to use checksums |
aae8618966a0c2d1ef120da2375b15eafb307b98bbab8df30e988b1921122db7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Aug 13, 2026.
Transparency logRelease files / bedrock_core-0.2.0-py3-none-any.whl
| Download URL | bedrock_core-0.2.0-py3-none-any.whl |
|---|---|
| Size | 104.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f82b0305c5b85e7ce44d5cace0bceb03a3d409cceecf9fd6af3aa9db9809529
|
|
BLAKE2b-256 checksum How to use checksums |
9eac7bbc19464d8d73395417a991020ad3ae959f5f21ff35c244f663a23c5438
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Aug 13, 2026.
Transparency log