Trust
Infrastructure ownership and controlled handoff.
What you build with Blockchain Central, you control. This page clarifies ownership boundaries, handoff practices, and where responsibility sits after delivery.
Ownership boundaries
What ownership means in a Blockchain Central engagement.
Ownership is not a footnote. It is built into how we scope, build, and deliver.
- 01
Client-controlled infrastructure
Deployed to environments the client controls, where scoped.
- 02
Source and build artifacts
Code, configuration, and deployment artifacts transferred at handoff.
- 03
Account and access boundaries
Cloud accounts, domains, and admin access are client-managed where applicable.
- 04
Operational visibility
Monitoring, logs, and operational state remain visible to the client post-handoff.
What you own
Deliverables that transfer to you.
After scoped delivery, these assets and controls sit with your team.
What we provide
Our role during and after delivery.
We build, deploy, document, and transfer. Ongoing operations are separate and only by explicit agreement.
- 01
Build and deploy
Implementation scoped to your constraints, deployed to your environment.
- 02
Documentation
Deployment docs, operational runbooks, and architecture context.
- 03
Training and handoff
Structured walkthrough of the system, access, and operational procedures.
- 04
Optional support
Ongoing support is available only when explicitly scoped and agreed.
What we do not claim
Hard boundaries that protect both sides.
These limitations exist to prevent misunderstanding and to keep responsibility where it belongs.
Handoff process
From build to controlled transfer.
A structured path so delivery becomes operational ownership, not a black-box handover.
Documentation
What is handed over at transfer.
Operational knowledge moves with the system so your team can run what we built.
- 01
Deployment documentation
Architecture diagrams, dependency maps, and environment configuration.
- 02
Operational runbooks
Procedures for common operations, monitoring, and troubleshooting.
- 03
Access and credentials
Admin accounts, API keys, and operator permissions transferred to your team.
- 04
Build and deployment context
CI/CD configuration, build scripts, and deployment procedures.
Operational visibility
Handoff should make system state and control paths legible.
Visibility means the client can inspect relevant deployment context, access records, and operating notes where they are in scope.
- 01
Operational records
Deployment notes, access records, and handoff context show what was transferred and who controls it.
- 02
Monitoring context
Where scoped, monitoring and alerting context is documented so the client team understands what to inspect.
- 03
Change context
Release notes and environment changes are captured where they affect client operation.
- 04
Support limits
Post-handoff support is separate unless it is included in the engagement.
Operator responsibility
Admin control moves with the system.
The handoff defines who operates the system, who approves changes, and where Blockchain Central's role ends.
- 01
Admin ownership
Admin roles transfer to client-designated operators at handoff.
- 02
Operator readiness
Runbooks and walkthroughs prepare the client's team to operate the delivered system.
- 03
Approval paths
Production changes and access decisions remain with the client after transfer.
- 04
Separate support scope
Ongoing administration, monitoring, or incident response requires a separate agreement.
Custody boundaries
Wallet, funds, and access separation.
In Web3 infrastructure, custody is not assumed. It is explicitly scoped and documented.
Frequently asked
Common questions about ownership and handoff.
- 01
Do you retain access after handoff?
No, unless a separate support scope is agreed. Production access is removed at sign-off.
- 02
What if we need changes later?
We can scope additional work or enhancements as a separate engagement.
- 03
Who owns the cloud account?
Where applicable, cloud resources are provisioned under your accounts. You retain full control.
- 04
Do you custody our funds?
No. We do not hold, manage, or operate client wallet keys or treasury funds.
- 05
What happens if something breaks after handoff?
Documentation and runbooks are provided for your team. Optional support can be scoped separately.
Book Infrastructure Strategy Call
Discuss ownership requirements, deployment boundaries, and what controlled handoff looks like for your infrastructure.