Current demo status, intended pilot deployment models, and minimum readiness checklist.
Current deployment
Current status: Replit-hosted browser demo only.
This is a demonstration surface. It is not a client deployment. It runs on Replit infrastructure
as a Node http server with no external API calls, no database, no authentication, and no
persistent storage. It is suitable for technical review and demonstration. It is not suitable
for handling real client data or production decisions.
Replit-hosted Node http server
No external API calls
No database dependency
No authentication layer
No framework dependency
Suitable for technical review
Suitable for demonstration
Not suitable for real client data
Not suitable for production decisions
Not a client deployment
Intended pilot deployment models
Mode A
Embedded library
CerbaSeal imported directly inside the client service at the decision boundary.
lowest network surface area
no separate service to operate
direct TypeScript/Node integration
requires engineering integration effort
Mode B
Internal HTTP service
CerbaSeal runs as an internal enforcement service. Workflow calls the enforcement endpoint.
cleaner separation of concerns
easier to audit independently
requires network and security controls
requires internal hosting
Mode C
Client-controlled pilot environment
Temporary controlled environment for the pilot period. Client controls infrastructure.
client controls data residency
EU-compatible if hosted in EU
requires data processing agreement
requires hosting review
In all pilot modes: client controls workflow data. Client controls deployment environment.
Evidence records should remain in client-controlled storage. CerbaSeal does not require
outbound network access.
What is not acceptable for a serious pilot
unmanaged public demo handling real client data
undefined data movement between systems
unclear evidence ownership
open-ended support without defined scope
no security review before client data touches the system
no defined rollback or update process
Minimum deployment readiness checklist
deployment environment selected (Mode A, B, or C)
data boundaries defined
logging destination defined
evidence retention period defined
security review complete for chosen environment
support window and scope defined
rollback and update process documented
version pinned and frozen for pilot
test suite passing (323 / 323, 15 test files)
pilot workflow scope frozen (one workflow, one decision path)
Fix / update process during pilot
Reproduce the issue locally with a test case
Apply fix to enforcement core
Run full test suite — confirm 0 regressions
Run pnpm demo:web:validate — confirm 98 / 98 assertions pass
Run pnpm demo:support:validate — confirm support readiness
Create new tagged version
Deploy to agreed environment
Verify replay and audit chain behavior against pilot scenarios
Document change in a change record
Current limitation notice:
This is a review-ready core demo, not a production client deployment.
The hosted demo at cerbaseal.replit.app is suitable for technical review only.
It must not be used to process real client data.