Open Design is a local-first, open-source AI design workspace for generating prototypes, decks, images, videos, and design-system-driven artifacts.
Launch in your Sealos workspace.
Start with the resources defined by the Open Design 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.
Open Design is a local-first, open-source AI design workspace for generating prototypes, decks, images, videos, and design-system-driven artifacts. This template deploys Open Design with a persistent workspace volume and an authenticated Nginx proxy on Sealos Cloud.
Open Design provides a browser workspace backed by a local daemon. The daemon serves the web UI, API routes, project files, plugin data, and generated artifacts from one container. On Sealos, the workspace is persisted at /app/.od so projects, conversations, media configuration, and generated outputs survive restarts.
The upstream Docker deployment exposes port 7456, uses a Docker volume for runtime data, and requires OD_API_TOKEN when the daemon binds to a public interface. This template runs an Nginx proxy in front of Open Design: Nginx exposes port 8080, protects public access with Basic Auth, forwards traffic to Open Design on port 7456, and injects the internal bearer token for /api routes.
The Sealos template includes the Open Design runtime image, a lightweight Nginx proxy, public HTTPS ingress, and persistent workspace storage. The upstream Docker deployment path is file-backed and self-contained, so the deployed stack consists of the runtime, proxy, ingress, and workspace volume.
Architecture Components:
74568080, enforcing Basic Auth and forwarding API requests with the generated bearer token/app/.od, including projects, conversations, generated artifacts, and local configurationConfiguration:
latest drift.OD_BIND_HOST=0.0.0.0, OD_PORT=7456, OD_WEB_PORT=7456, and a generated OD_API_TOKEN match the upstream cloud runtime requirements.OD_ALLOWED_ORIGINS is set to the generated Sealos HTTPS domain so browser requests are accepted behind Ingress.auth_username and auth_password configure Nginx Basic Auth for the public Open Design URL./api/ with Authorization: Bearer <generated token> so browser API calls work through the public Sealos domain.License Information:
Open Design is licensed under Apache-2.0.
Sealos is an AI-assisted Cloud Operating System built on Kubernetes that unifies the entire application lifecycle, from development in cloud IDEs to production deployment and management. By deploying Open Design on Sealos, you get:
auth_username defaults to admin; auth_password is generated automatically, and you can replace it with your own strong password before deployment.auth_username and auth_password values from the deployment form.Account setup happens in the deployment form: set auth_username and auth_password, then the proxy uses those credentials for the public app URL. Open the generated app URL and sign in through the browser Basic Auth prompt. The username defaults to admin, and the generated password appears in the deployment form unless you replace it before deployment.
After authentication, Open Design shows its first-run onboarding screen. Choose a runtime option or click Skip to enter the workspace, then configure BYOK providers, plugins, design systems, and local workspace settings inside Open Design.
The template was live-tested on Sealos with 100m CPU / 256Mi memory for the Open Design container, 100m CPU / 128Mi memory for the Nginx proxy, and a 1Gi persistent workspace volume. During the smoke test, the Open Design container used about 30m CPU and 67Mi memory, while the proxy used about 1m CPU and 22Mi memory.
After deployment, you can configure Open Design through:
auth_username or auth_password.Open Design stores local workspace state on a single persistent volume, so keep the application at one replica unless you have validated a multi-replica storage and session strategy for your own deployment.
To increase capacity:
This template uses an Nginx proxy to inject the generated API token for /api/ routes. If API calls fail, confirm the proxy Deployment is running and still has the generated Nginx configuration mounted.
Use the auth_username and auth_password values from the deployment form. These credentials belong to the public proxy layer.
Open Design shows onboarding on first launch. Select a runtime option or click Skip to enter the workspace, then configure model providers and plugins from the UI.
Confirm the StatefulSet still mounts the persistent volume at /app/.od. Workspace data is stored there.
This Sealos template is provided under the repository license. Open Design is distributed under the Apache-2.0 license.
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.
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.
Host n8n workflow automation on Sealos with persistent storage and HTTPS webhooks. Choose PostgreSQL and Redis-backed queue mode as your workflows grow.
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.