Build production-ready tools templates with Sealos.

A privacy-focused, local-first, open-source workspace for notes, docs, whiteboards, and team knowledge management.

Drizzle Studio (Gateway) is a self-hosted, browser-based interface for exploring and managing your database schema using the Drizzle ORM ecosystem. It acts as a gateway between your database and Drizzle Studio’s frontend, enabling secure connections, schema introspection, and query execution directly from your own infrastructure instead of relying on a public service.
Launch in your Sealos workspace.

Start with the resources defined by the Drizzle Studio (Gateway) 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.
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.