Deploy AI support on Sealos — a developer-friendly K8s "desktop"

What Sealos is#

Sealos is an open-source Kubernetes desktop (labring/sealos) that gives developers:

• A macOS-style console
• One-click databases (Postgres / MySQL / Redis) via app market
• In-browser Devbox dev environment
• Multi-region in China (Beijing / Hangzhou / Guangzhou)
• Data residency by default

The App Launchpad is a simplified front for K8s Deployments — fill a few fields and any Docker image starts.

Fits#

• China-resident projects
• Want K8s without YAML
• Price-sensitive teams (Sealos is typically 30-50% cheaper than Aliyun)
• Already in the domestic stack (1Panel, Wails, etc.)

Deployment#

1. Sign up#

Open https://cloud.sealos.io, register, pick a region.

2. Chatwoot via App Launchpad#

Console → App Launchpad → New app:

Image: chatwoot/chatwoot:v4
Port: 3000
CPU: 1
Memory: 2 GB

Env:
  RAILS_ENV: production
  FRONTEND_URL: https://chat.your.com
  POSTGRES_HOST: chatwoot-db.ns-xxx.svc
  POSTGRES_USERNAME: chatwoot
  POSTGRES_PASSWORD: <strong-pw>
  POSTGRES_DATABASE: chatwoot_production
  REDIS_URL: redis://chatwoot-redis.ns-xxx.svc:6379
  SECRET_KEY_BASE: <openssl rand -hex 64>

3. Postgres + Redis#

Database panel → one-click:

• Postgres 16 — 2 GB RAM, 20 GB storage
• Redis 7 — 512 MB

4. Sidekiq worker#

Duplicate the Chatwoot image, change command to bundle exec sidekiq -C config/sidekiq.yml.

5. Dify#

Same pattern — start dify-api, dify-worker, dify-web, weaviate. Or search “Dify” in the app market for a one-click install.

6. Custom domain + TLS#

App Launchpad → Network tab:

• Add custom domain (CNAME to Sealos-provided host)
• Enable TLS (auto-signs)

Cost (Hangzhou)#

Resource	Spec	Monthly
Chatwoot app	1C/2G	~¥40
Sidekiq worker	0.5C/1G	~¥20
Dify API + Worker	2C/4G	~¥80
Postgres	2GB RAM	~¥50
Redis	512MB	~¥15
Weaviate	1C/2G	~¥40
Egress	100GB	~¥30
Total		~¥275 / mo

About 30-40% cheaper than Aliyun ECS directly.

Advanced: Devbox for in-browser dev#

Sealos Devbox runs VS Code in the browser, connected to your cluster:

git clone https://github.com/your/dify-prompts
code .  # edit in the browser

Iterate Dify prompts against the in-cluster Dify API without local setup.

Pitfalls#

• China compliance — real-name + ICP filing required for public domain access
• Persistence — App Launchpad lacks default PVCs; attach for attachment dirs
• Cross-namespace — services need .svc suffix
• TLS — DNS must resolve before certs issue