There’s a moment everyone who builds software knows: the new project is greenlit, the idea is clear. And then a week or two passes in which you write not a single line of business logic. Instead: set up the cloud account, stand up a Kubernetes cluster, write Terraform modules, build CI/CD pipelines, wire up the database, maintain Helm charts, manage secrets. Always the same. Always from scratch.
That’s the part I got tired of, so I built VelaAtlas.
What VelaAtlas does
VelaAtlas is a product that builds complete, production-ready software projects and delivers them to your GitHub account. You configure your setup in an online configurator (cloud provider, database, services, frontend) and get a ready-to-run code kit in return: cloud infrastructure, backend, an optional frontend and finished CI/CD pipelines. From click to delivery takes less than an hour.
No empty git init, no "Hello World" you then have to flesh out yourself, but the foundation you’d otherwise hand-build in the first two weeks of every project. Fully built, in your name, in your GitHub account.
How it works
Three steps:
- Configure. In the configurator you pick the cloud (Google Cloud or AWS), whether you need a PostgreSQL database, how many microservices (1 to 5), whether an Angular frontend is included, mono- or multi-repo, and how many stages (dev/staging/prod). The price updates live with your choices.
- Enter your data. After purchase, a short form asks for your app name, your cloud tokens and the service names.
- Get it delivered. The build pipeline assembles your personalized repositories, creates them privately in your GitHub account, stores the cloud credentials as encrypted secrets and builds a personalized PDF handbook. When everything is done, you get an email with an overview of all repos or a download link.
If you’d rather watch than read, there’s a live walkthrough at velaatlas.com/demo that shows the whole flow step by step.
What’s inside
The delivered code is no toy. The tech stack:
- Backend: Spring Boot on current Java, optionally with a Spring Cloud Config Server
- Frontend: optional Angular on TypeScript
- Database: optional PostgreSQL per service, including schema migrations (Liquibase or Flyway, your choice)
- Infrastructure: Terraform modules for GCP (GKE, Cloud SQL, Artifact Registry) or AWS (EKS, RDS, ECR)
- Deployment: Helm charts per stage, ArgoCD, Kubernetes
- CI/CD: GitHub Actions with OIDC, so no password handling and encrypted secrets
- Documentation: an automatically created PDF handbook in your language
Anything you don’t need you simply leave out in the configurator. No frontend, no database, no config server? Then it’s not in the delivered code either. You pay for and get only what you actually need.
Who it’s for
VelaAtlas is aimed at developer teams and companies that need a professional setup without burning weeks on boilerplate, cloud configuration and pipeline plumbing. It’s a strictly B2B offer. The code then lives entirely in your GitHub account and on your cloud. VelaAtlas is not a SaaS or hosting product, but a one-time delivery. What you do with it is yours.
Why I built it
Honestly: because I’d have needed it myself. That same recurring startup work is exactly the kind of repeatable complexity you should automate instead of redoing by hand in every project. What started internally as a collection of templates is now a product anyone can use.
If that sounds interesting, take a look at VelaAtlas or jump straight into the demo. Happy to answer any questions.