Objective
Provide an operator-grade runbook for the local portal package and clearly separate local capabilities from openibank.com-exclusive services.
Local Portal Operations
Production TrackOperating the downloadable OpeniBank local web portal for self-hosted management of banking, trading, agents, and receipts.
Deployment Scope
The local portal is a self-hosted control plane focused on local runtime operations. It includes wallet and ledger visibility, trade controls, node monitoring, and receipt verification.
The package is intentionally local-first. Core workflows do not depend on openibank.com services and remain usable in private-network deployments.
Bootstrap and Runtime
Operators install from source, initialize environment state, and launch the runtime with portal mode enabled. Startup confirms core services and endpoint status.
Recommended production posture includes explicit data directory management, encrypted backup schedule, and periodic restore drills.
Feature Boundary and Upgrade Path
Local portal scope excludes hosted campaign automation and other cloud-exclusive account features. This keeps sovereignty and deterministic local operation as the baseline.
When teams need hosted scale, the same operating model can graduate to hosted node tiers without changing receipt, permit, and commitment semantics.
Interfaces
Portal UI
Dashboard, trade control, agent fleet, receipts, nodes, and settings pages under /portal
Install Flow
Clone/build/init/start sequence documented in Local Portal download page
Production Checkpoints
- ✓Portal starts with all local core services healthy
- ✓Receipt verification succeeds from portal workflow
- ✓Backup + restore drill reproduces state without replay gaps
- ✓Local-only and cloud-exclusive boundaries are documented for operators
Continue exploring