After the build
Own it, or we run it.
Two ways to operate the same implementation. Neither is the "right" answer, it depends on your team, your IT capacity and how much you want to change things yourself.
We design and build the scoped implementation, train your team and hand over the agreed documentation, configuration, prompts and skills.
- Infrastructure
Your team
Runs on servers or cloud accounts you control. Your team (or your IT provider) keeps them patched and available.
Stays with you either way
You decide where it runs and can see what it runs on.
- Accounts & access
Your team
Model-provider, hosting and integration accounts are in your name; you manage credentials.
Stays with you either way
You can revoke our access to your systems.
- Monitoring
Your team
Your team watches the agreed health checks and review queues.
Stays with you either way
You can see activity logs for your workflows.
- Approvals
Your team
Your people approve the steps marked for human review.
Stays with you either way
Approval points are yours in both models.
- Maintenance & improvement
Your team
Your team updates prompts, skills and configuration; we're available for paid support.
Stays with you either way
Changes to scope are agreed with you first.
- Documentation
Your team
We hand over the agreed documentation, configuration, prompts and skills at the end of the build.
Stays with you either way
Custom deliverables we create for you are described in the agreement.
Portability, precisely.
"No lock-in" is too simple a promise. Here is what's yours, what isn't ours to give, and what gets agreed up front.
Custom deliverables
The configuration, prompts, skills, workflow logic and documentation we create for you, as described in your agreement.
Open-source platform
OpenClaw is MIT-licensed open source. Anyone can run it; its license terms come from the project, not from us.
Third-party services
Model providers, hosting, CRMs and other software have their own accounts, licenses, pricing and terms. Those relationships are separate from ours.
Transitions
Handover scope, timing and any transition support are agreed during discovery, not assumed to be immediate.