Self-hosted synchronization backend for end-to-end encrypted Happy clients for Claude Code.
Launch in your Sealos workspace.
Start with the resources defined by the Happy Server template. Review CPU, memory, persistent storage, and network allocations for every service in Canvas. Capacity needs depend on your data and workload; monitor usage as they grow.
Template configuration and setupUse the application URL or connection details shown in Canvas. Follow the deployment guide for first-time account setup or client configuration, and keep generated credentials available for that step.
Sealos monthly plans include compute, memory, storage, and traffic. Size your plan for all deployed services. Software licenses and external AI or API services may have separate terms and charges. Confirm the applicable plan and optional charges in Cost Center.
Compare Sealos resource plansFor current cloud charges, refer to Sealos plan pricing. Upstream documentation may reference earlier billing models.
Happy Server is the self-hosted synchronization backend for open-source, end-to-end encrypted Happy clients for Claude Code. Clients encrypt conversation and session data before it leaves the device; the server stores and relays encrypted payloads, coordinates authentication, and keeps devices in sync through HTTP APIs and WebSocket connections.
This Sealos template deploys Happy Server with managed PostgreSQL, Redis, S3-compatible Object Storage, HTTPS ingress, and an App Launcher shortcut.
The template creates these resources:
ghcr.io/yangchuansheng/happy-server pinned by digest.3005./health, which validates database connectivity.happy-server database and required tables before the application becomes ready.200m CPU and 256Mi memory after deployment testing; 128Mi was rejected because the Node.js process was OOM-killed during startup.Sealos gives this template managed runtime primitives that fit Happy Server well:
Open Happy Server on the Sealos App Store, then click Deploy Now.
The template generates:
app_name: Kubernetes resource name prefix.app_host: public hostname prefix.seed: random server-side secret used by Happy Server.The generated values are safe defaults for a fresh deployment. Change app_name or app_host only if you need a stable name.
Click Deploy. Sealos creates the object storage bucket, PostgreSQL cluster, Redis cluster, database initialization Job, application Deployment, Service, Ingress, and App Launcher entry.
After deployment completes, open the generated Sealos App URL. You can also verify the health endpoint:
curl https://<your-happy-server-domain>/health
A healthy response looks like:
{"status":"ok","service":"happy-server"}
| Item | Source | Purpose |
|---|---|---|
DATABASE_URL | Sealos PostgreSQL secret | Connects Happy Server to the happy-server database. |
REDIS_URL | Sealos Redis secret and service DNS | Enables Redis-backed real-time coordination. |
S3_ACCESS_KEY, S3_SECRET_KEY, S3_BUCKET, S3_HOST | Sealos Object Storage secrets | Enables artifact and file storage. |
PUBLIC_URL | Generated Sealos HTTPS domain | Public base URL for the service. |
HANDY_MASTER_SECRET | Generated template seed | Server-side secret material. |
The default template runs one Happy Server replica. Increase replicas only after confirming the Redis-backed real-time workflow and your client traffic pattern. PostgreSQL and Redis are deployed with persistent storage and Sealos-managed service endpoints.
*-pg-init Job to finish.*-redis-redis-redis.256Mi or higher. A 128Mi test limit was insufficient for the current Node.js image.publicRead, because Happy Server returns public object URLs.Happy Server is released under the MIT License. This Sealos template follows the license of the template repository.
A shorter path from an app you want to an app you can run. Sealos brings deployment and ongoing operations into one place.
Start with a ready-made template. Review its configuration and launch from the Sealos console.
Run on managed infrastructure with built-in workload scheduling and recovery.
Give your application a public HTTPS endpoint with certificates managed for you.
Keep application data on persistent volumes across container restarts.
Adjust CPU, memory, and replicas from the console as your workload changes.
Sealos provisions the resources defined by your template and brings them together in your workspace.
Container workloads with configurable CPU, memory, and replicas.
An address for your app, with managed TLS certificates.
A database provisioned alongside your app when the template calls for one.
Storage for the files and data your application needs to keep.
Application settings and secrets configured in one place.
Inspect container logs and resource usage from the console.
Resources and their configuration vary by template. Review the deployment form for this app’s exact setup.
Explore more production-ready templates.
Build production-ready ai templates with Sealos.
Open Design is a local-first, open-source AI design workspace for generating prototypes, decks, images, videos, and design-system-driven artifacts.
Build production-ready ai templates with Sealos.
Host OpenClaw's AI agent gateway on Sealos with a browser control panel, token authentication, and persistent storage for configuration and workspaces.
Build production-ready ai templates with Sealos.
Open-source AI model gateway compatible with the OpenAI API, with multi-provider routing, quota management, channel orchestration, and an admin dashboard.