Software Project Starter Kit

Description

What You Get

The Software Project Starter Kit generates a complete, production-ready software project for you – fully automated in under 60 minutes. You configure your stack (cloud provider, services, stages, repository mode), purchase the kit and enter your cloud credentials. Our build pipeline handles the rest: finished GitHub repositories, fully configured and deployment-ready.

Repositories – Ready to Use

After generation, you will find coordinated repositories in your GitHub account (four in monorepo mode, one separate repo per component in split mode):

What's Included in the Stack

• Spring Boot Backend – Production-ready microservice with REST API, health checks, Actuator endpoints and SpringDoc OpenAPI documentation. Containerized with Google Jib – no Dockerfile required.
• Angular Frontend – Single Page Application with Material Design, routing and optimized build pipeline. Served via Nginx with reverse proxy to the backend.
• Spring Cloud Config Server – Centralized configuration management. All services read their configuration from a dedicated config repository – changes without redeployment.
• PostgreSQL Database – Cloud-managed (Cloud SQL or RDS) with Liquibase or Flyway migrations and IAM authentication. No passwords, no secrets in code.
• Terraform Infrastructure – Complete cloud infrastructure as code: VPC/networking, Kubernetes cluster (GKE/EKS), container registry, IAM with Workload Identity/OIDC and state backend (GCS/S3).
• Helm Charts – Kubernetes deployments for all services with Ingress-NGINX, cert-manager for TLS and Cloud SQL Proxy or RDS sidecar for database access.
• CI/CD Pipelines – GitHub Actions workflows for backend, frontend and Terraform. Automatic build, test and push to the container registry on every commit.
• ArgoCD GitOps – Automatic deployment to Kubernetes. Change the Helm chart, push, ArgoCD syncs – no more manual kubectl apply.
• Docker Compose – Local development environment with backend, frontend, Config Server and PostgreSQL. One docker compose up and you're developing locally.

Multi-Cloud: GCP and AWS

Choose Google Cloud Platform, Amazon Web Services or both. The infrastructure is generated identically – same architecture, same security standards, same CI/CD pipelines. Only the cloud-specific services differ:

Modular Design

Not every project needs everything. Choose what you need when placing your order:

• Database – PostgreSQL with Liquibase or Flyway migrations and IAM login. Without this option, you get a stateless service with no database dependency.
• Config Server – Centralized configuration via Spring Cloud Config. Without this option, each service reads its configuration locally from application.yaml.
• Angular Frontend – Complete frontend with Nginx proxy. Without this option, you get a backend-only project.
• Multiple Backend Services – Generate up to 5 microservices per project. Each service gets its own controller, POM, Dockerfile, Helm chart and CI/CD workflow.
• Deployment Stages – Choose exactly the environments you need (dev, staging, prod). For each stage, Helm values, Terraform configurations and ArgoCD apps are generated.

The generated files (Docker Compose, Maven modules, Helm charts, CI/CD workflows) automatically adapt to your selection – no dead dependencies, no dead code.

Repository Mode

Choose the repository strategy that fits your team:

• Monorepo – All services, frontend and Config Server in one repository with a shared parent POM. Ideal for small teams and fast iterations.
• Split Repos – Each component gets its own repository with a standalone POM, its own Maven Wrapper and its own CI/CD workflows. Ideal for larger teams with independent deployment cycles.

CI/CD Strategy

Two branching models are available:

• Multi-Branch – Feature branch → Pull Request → Merge → automatic build and deployment to all stages. One workflow for everything (gcp-ci.yml / aws-ci.yml).
• Single-Branch – Push to main automatically triggers build + push. Deployment to individual stages is triggered separately via workflow_dispatch – full control over the rollout.

Included Helper Scripts

Every generated project includes shell and batch scripts for the most common post-delivery tasks:

• Cloud Bootstrap – init-script.sh sets up your cloud account once: IAM roles, OIDC federation, Terraform state backend, service accounts and secret manager. One command – all prerequisites fulfilled.
• Infrastructure Deployment – deploy.sh runs the complete Terraform deployment: Kubernetes cluster, database, ingress controller, ArgoCD, DB initialization and Helm values – with retry logic and stage-specific hostnames.
• Change Cloud Configuration – update-aws-config.sh and update-gcp-config.sh update account ID, region and registry URLs across all repositories at once. No manual searching through YAML files.
• Switch Hostname – update-hostname.sh switches between IP-based nip.io address (development) and custom domain (production) – one command for all repositories.

All scripts are idempotent (safe to re-run) and available as .sh + .bat – for Linux, macOS and Windows.

Current Versions

Backend

Frontend

Database

Infrastructure & Terraform

Kubernetes & Deployment

CI/CD & Build

How It Works

1. Configure – Choose your cloud provider (GCP, AWS or both), optional components (database, Config Server, frontend), repository structure and branching strategy (multi-branch or single-branch).
2. Order & Pay – The price is calculated based on your selection.
3. Enter Project Details – After purchase, you receive a form for your project settings (app name, repository owner). You can optionally provide cloud credentials and a GitHub token – then repositories and CI/CD secrets are automatically set up for you. Without these details, you receive the finished project as a download – you then enter secrets and project IDs yourself in the generated configuration files.
4. Automatic Generation – Our build pipeline creates your project. If desired, the GitHub repositories are created and CI/CD secrets are configured.
5. Get Started – You receive an email with a download link and can start developing immediately.

Why It's Worth It

An experienced DevOps engineer typically needs 2–4 weeks to manually set up comparable infrastructure. That quickly adds up to costs of 30,000+ EUR – per project, starting from scratch every time.

The result is rarely consistent: missing health checks, hardcoded secrets, no IAM integration, CI/CD pipelines without OIDC – typical shortcuts under time pressure. With the Software Project Starter Kit, you get an architecture in under 60 minutes that avoids these mistakes from the start: OIDC instead of passwords, IAM authentication instead of database secrets, GitOps instead of manual deployment. Automated, reproducible and production-ready from day one.

Cost Comparison