SigilbaseDjango audit logs, sealed as they arrive.
Sigilbase will collect audit logs from Django into a chained, signed ledger: every collection receipted, every gap declared, and evidence your auditor verifies offline without an account.
Bridges ship in waves, and the Django bridge is in the second. Until then, your application can write events through the Sigilbase SDK or the events API today.
- Status. Second wave.
- Collected by. A bridge inside your application.
- Connects with. Your application's own Sigilbase key, through the SDK the bridge depends on.
- Category. Application frameworks.
What can be ingested from Django
Each stream below becomes its own sequence in the ledger, with the record kept exactly as Django gives it and a hash of those bytes beside it. Snapshots are read on a cadence and the differences between them dated.
-
Event stream
Django-auditlog / django-simple-history signal bridge; logging handler.
How it will be collected
A small open-source package inside your application will forward the audit trail it already keeps through the Sigilbase SDK; nothing reads your systems from outside.
Stream and credential names follow the vendor's documentation as read in October 2026; the connector's build confirms them.
The evidence model
What every connector and receiver ships with, whatever the source:
- A receipt per collection: what was asked for, what arrived, the cursor before and after
- A declared gap for any interval nothing covers, never a blank
- A daily settlement once late records can no longer arrive
- The raw record, byte for byte, with its hash
- An evidence bundle anyone can verify offline
What you get
-
Sealed as it arrives
Every record is hashed and chained to the one before; every few minutes the chain is sealed into a signed checkpoint. A changed, deleted or reordered record fails verification at that exact point.
-
Continuity you can show
The receipts chain too, so an auditor sees not only the records but that nothing between them went uncollected, and where a gap was, that it was declared.
-
Verified without us
An export carries the open-source verifier. It runs offline, checks the chain, the receipts and the gaps, and needs no Sigilbase account. How the service is run.
Questions about Django
-
Does Sigilbase support Django?
Bridges ship in waves, and the Django bridge is in the second. Until then, your application can write events through the Sigilbase SDK or the events API today. Whatever arrives is written to a chained, signed ledger whose evidence anyone can verify offline with the open-source verifier, without a Sigilbase account.
-
What Django data can Sigilbase ingest?
Event stream: Django-auditlog / django-simple-history signal bridge; logging handler.
-
How will Django evidence be collected and verified?
A small open-source package inside your application will forward the audit trail it already keeps through the Sigilbase SDK; nothing reads your systems from outside. Every collection will be receipted in the connection's own stream: what was asked for, what arrived, and the cursor before and after. An interval nothing covers will be declared as a gap, never left blank. Exports carry the standalone verifier, which checks the chain, the receipts and the gaps offline.
Start recording provable history
Chained, sealed, independently verifiable audit logs, from the first event. Free while Sigilbase is in beta.
Questions first? Write to hello@sigilbase.io.