Catalog update
47 new stacks: Java, .NET, Rust, JavaScript frameworks, and open-source apps
The Wodby stack catalog has grown by 47 stacks. Fourteen are for building your own applications: new languages and frameworks with matching boilerplates. The other 33 are open-source applications and infrastructure you can deploy as they are.
Every application on Wodby starts from a stack: a reusable set of services, links, and configuration that your app environments share. This update adds Java, .NET, Rust, and more JavaScript frameworks for code you write yourself, and ready-to-run stacks for team chat, helpdesks, workflow automation, Git hosting, single sign-on, search, event streaming, analytics, monitoring, and tracing.
Framework stacks with boilerplates
Each of these stacks comes with a public boilerplate. When you create an app, Wodby can copy the boilerplate into a new GitHub or GitLab repository, so you start with working code that already builds and deploys on Wodby. If you already have a project, connect its repository instead.
Java web apps and APIs with Spring Boot. PostgreSQL is enabled and connected to the app. Valkey, email, and document rendering are included and switched off until you need them.
Boilerplate: wodby/spring-boot-boilerplate
.NET web apps and APIs. PostgreSQL, Valkey, email, and document rendering are already connected and switched off, so a new app starts small.
Boilerplate: wodby/aspnetcore-boilerplate
PHP apps on Symfony, served by PHP-FPM behind Nginx. PostgreSQL and Mailpit are enabled; switch to OpenSMTPD for real email delivery.
Boilerplate: wodby/symfony-boilerplate
Full-stack React apps with TanStack Start on Node.js. Add PostgreSQL, Valkey, or email when the app needs them.
Boilerplate: wodby/tanstack-start-boilerplate
Vue apps with Nuxt on Node.js. PostgreSQL, Valkey, email, and document rendering are included and switched off until you need them.
Boilerplate: wodby/nuxt-boilerplate
Svelte apps with SvelteKit on Node.js, with the same optional PostgreSQL, Valkey, email, and document rendering.
Boilerplate: wodby/sveltekit-boilerplate
Content sites and server-rendered apps with Astro on Node.js, with the same optional services.
Boilerplate: wodby/astro-boilerplate
A headless CMS on Node.js. PostgreSQL and persistent upload storage are enabled; email is optional.
Boilerplate: wodby/strapi-boilerplate
All eight work with dev workspaces, so you or an AI agent can change code against a running copy of the app before you release it.
Java, Kotlin, and Rust runtimes
Not every project uses a framework we ship a stack for. These runtime stacks run any app written in the language, with the same optional PostgreSQL, Valkey, email, and document rendering services already connected.
They join the existing Node.js, PHP, Python, Ruby, and Go stacks. All three are ready for dev workspaces.
React, Vue, and Angular frontends
Wodby builds the app from your repository and serves the compiled site with Nginx. Each stack has a boilerplate and works with dev workspaces.
Self-hosted apps for teams
These stacks deploy a complete open-source application, with its database, cache, storage, and workers already set up. Use them when you want the tool itself rather than code to build on.
Collaboration and support
Team messaging (Team Edition) with PostgreSQL, persistent file storage, and optional email.
File sharing and collaboration with PostgreSQL, Redis, persistent storage, and optional email.
A customer support inbox with background workers, PostgreSQL, Redis, and shared attachment storage.
A helpdesk with PostgreSQL, Redis, Memcached, optional Elasticsearch search, and outbound email.
Business and automation
Workflow automation with PostgreSQL, persistent data storage, and optional outbound email.
Business applications on Nginx and PostgreSQL, with shared storage for the filestore and optional outbound email.
Business intelligence dashboards and data questions, with PostgreSQL for application data and optional outbound email.
Remote access and private networks
Your own remote desktop server. Devices connect over WebSocket through the app’s HTTPS domain, so no extra ports need to be opened. Run the Show client settings action to get the values for the RustDesk app.
Your own NetBird server for a WireGuard-based private network that connects devices, servers, and teams.
Communities, publishing, and learning
A community forum with PostgreSQL, Redis, and outbound email.
Blogs and newsletters with MySQL, persistent content storage, and transactional email.
A learning management system on PHP and Nginx with MariaDB, shared course-file storage, and a cron worker. Moodle is installed during the first deployment with the admin account you set.
Identity, backends, and code hosting
Single sign-on and user management for your applications, with PostgreSQL for identity data.
A self-hosted application backend: PostgreSQL, Auth, REST, Realtime, Storage, and Studio.
GitLab Community Edition for Git repositories and CI/CD, with PostgreSQL, Valkey, email, and an optional GitLab Runner.
Lightweight Git hosting with PostgreSQL, persistent repository storage, and email notifications.
Community-driven Git hosting with PostgreSQL, persistent repository storage, and email notifications.
Databases and search
Deploy a database or search engine as its own app and connect other apps in the same cluster to it, or add the same services to a stack you maintain.
Relational database with an optional phpMyAdmin interface.
Document database with an optional Mongoku interface for browsing data.
Column-oriented database for analytics queries.
Full-text search and analysis, with optional Kibana.
Full-text search and analysis, with optional OpenSearch Dashboards.
Fast, typo-tolerant search with persistent index storage.
Data pipelines and streaming
Durable event streaming for messaging and data pipelines.
Distributed analytics and batch jobs, with a master and a worker.
Schedule and monitor data workflows, with PostgreSQL for workflow metadata.
They complement the existing Dagster, RabbitMQ, and ZooKeeper stacks.
Monitoring, logs, and tracing
Dashboards for your metrics and logs, with persistent storage for configuration.
Store and query logs, with an optional Grafana already connected.
Time-series metrics storage, with an optional Grafana already connected.
Distributed tracing: the OpenTelemetry Collector receives traces, Tempo stores them, and Grafana shows them.
Together with the existing Prometheus stack, you can run your own metrics, logs, traces, and dashboards next to your apps.
AI and developer tools
Run browser-based coding agent sessions on your own cluster, with persistent storage for projects and session state.
A self-hosted chat interface for OpenAI-compatible model APIs, with PostgreSQL for users and chat history.
vLLM Preview
Serve a language model through a private, OpenAI-compatible API. Requires a cluster with GPU nodes. The stack is not exposed publicly: reach it through Private App Access or a private network. The inference examples show how to call it.
Available now
All 47 stacks are public. Browse the stack catalog to see what each one contains, then open Stacks in the Wodby dashboard and use Add stack to copy the one you want into your organization or project.
The copy is yours to change: add services, edit configuration, and publish your own revisions. It stays linked to the catalog version, so you can pull in later catalog updates or keep it as it is. The stacks documentation covers how revisions, links, and updates work.
Most stacks also have a guide in the stack catalog documentation that walks through creating the environment, connecting its services, and backups. The dashboard links a stack's guide from the stack itself, including your copy.
You can also ask Wodby Agent to recommend a stack for your idea and create the app for you.