Documentation

Templates & Blueprints

Start faster with reusable templates and preconfigured application blueprints.

Templates help teams start from a known-good project structure instead of building every application from scratch.

Overview

In NebuaCloud, templates are intended to speed up the first version of a service or application. The current documentation focuses on starter templates and reusable structure, not on a separate hosted template registry or template API.

What Templates Are Good For

Bootstrapping frontend, backend, and full-stack projects
Standardizing folder structure across teams
Reusing deployment manifests or Helm values
Starting from conventions your team can edit afterward

Template Categories

Frontend Starters

Use frontend templates when you need a ready-made application shell with the tooling already in place.

Examples include React, Vue, Next.js, Astro, Nuxt, and other common frontend stacks.

Backend Starters

Backend templates give you a starting point for API services and server-side applications.

Examples include Express, Fastify, FastAPI, Django, Spring Boot, .NET Web API, and other backend frameworks.

Full-Stack Starters

Full-stack templates combine a frontend and backend foundation for teams that want to start from an integrated project structure.

Recommended Workflow

Choose the closest template to your target stack
Generate or copy the starter project
Rename the application and update environment-specific values
Remove unused services or dependencies early
Connect the project to your pipeline and deployment flow

What To Customize First

Application name and branding
Environment variables
Secrets and credentials handling
Database or storage settings
Deployment manifests, Helm values, or container settings

Best Practices

Treat templates as a starting point, not a finished production design
Remove unused packages and example code before deploying
Keep deployment settings aligned with your real cluster configuration
Document any team-specific changes you apply on top of the template

Troubleshooting

Template Feels Too Generic

Start from the closest matching stack and trim it down
Prefer small customizations over building a brand-new starter too early

Deployment Fails After Customization

Recheck environment variables and image configuration
Validate Helm values or Kubernetes manifests after editing
Compare your changes against the original template structure