nacre.sh vs Self-Hosting OpenClaw: Full Comparison 2026

The self-host OpenClaw vs managed hosting question is one of the most common debates in the OpenClaw community. Both approaches work. The right choice depends on your technical skills, available time, privacy requirements, and budget. This comparison covers every relevant dimension to help you decide.

Setup Time

nacre.sh: 5 minutes from signup to running instance. No terminal access required. The platform provisions, configures, and secures your instance automatically.

Self-hosted: 2–8 hours for a typical first-time deployment on a VPS. You'll need to install Docker (or set up a native Python environment), configure nginx as a reverse proxy, obtain and configure TLS certificates, set up a systemd service, and configure firewall rules. More if something goes wrong.

Ongoing Maintenance

nacre.sh: Zero ongoing maintenance. Security patches are applied automatically. TLS certificates renew automatically. Backups run nightly without intervention. If a new OpenClaw version is released, nacre.sh rolls it out to instances on a tested schedule.

Self-hosted: Regular maintenance required. You need to monitor for OpenClaw releases, test updates before applying them, renew certificates (Certbot automates this but still requires monitoring), manage backup jobs, and respond to security disclosures — sometimes urgently.

Security

nacre.sh: Dedicated instance (no shared resources), automatic security patches, managed firewall, TLS on all connections, nightly backups to Cloudflare R2. nacre.sh patched CVE-2026-25253 across all customer instances within 4 hours of disclosure.

Self-hosted: Security is entirely your responsibility. Misconfigured firewalls, expired certificates, unpatched vulnerabilities, and poor credential management are common failure modes for self-hosted instances. Sophisticated users can achieve high security, but it requires consistent attention.

Cost

Item	nacre.sh	Self-Hosted (VPS)
Infrastructure	Included	$12–20/month
Backups	Included (R2)	$2–5/month
Domain + TLS	Included	$1–2/month
Monitoring	Included	$5–10/month
Maintenance time	0	2–5 hrs/month
Total	$12	$50–100 effective

Privacy and Data Control

nacre.sh: Your data lives in nacre.sh's infrastructure. nacre.sh has access to your container (though they are contractually prohibited from accessing your data without consent). Your LLM API keys are stored encrypted. This is sufficient for most personal and business use cases.

Self-hosted: Complete control over your data and infrastructure. Required for some compliance frameworks (HIPAA, certain GDPR interpretations) and for users in regulated industries.

Scalability

nacre.sh: Add more instances through the dashboard. Each instance is independent and billed separately.

Self-hosted: Requires manual scaling — spinning up new VPSes, load balancers, and managing multiple deployments.

Verdict

Choose nacre.sh if: You value your time, you're non-technical or getting started, you want guaranteed uptime without oncall responsibilities, or you're running production agents.

Self-host if: You need full data sovereignty, you're building infrastructure skills, you already have a server running other services, or you have very specific compliance requirements.

Frequently Asked Questions

Can I migrate from self-hosted to nacre.sh later?

Yes. Export your openclaw.json and memory directory from your self-hosted instance, then use the nacre.sh web terminal to import them into your new managed instance.

Does nacre.sh see my LLM API keys?

Your API keys are stored encrypted in your isolated instance environment. nacre.sh infrastructure staff cannot view plaintext keys under the platform's access control policies.

What support is available if something breaks?

nacre.sh provides email and live chat support. Self-hosted support relies on the OpenClaw community Discord, GitHub issues, and your own troubleshooting.