Frequently Asked Questions

A ready-to-use source code kit for production-grade cloud infrastructure: 1–5 Spring Boot microservices, optional Angular frontend, optional PostgreSQL database per service with schema migrations, optional Spring Cloud Config Server, plus Helm charts per stage, Terraform modules for GCP or AWS, GitHub Actions CI/CD, and a personalized PDF handbook.

Either as a direct push to your GitHub account (private repositories are created for you) or as a ZIP download. You choose the option in the order form.

Typically 1 to 2 hours after you submit your cloud data. You will receive an email as soon as the build is done — with an overview of all repositories or a download link for the ZIP.

Basic knowledge of Java/Spring Boot, Git, and cloud (GCP or AWS) is helpful to adapt and operate the delivered code. The included handbook walks you step by step through quickstart, repository structure, CI/CD, and deployment.

Yes — an automatically generated ~15-chapter PDF handbook in your chosen language (German, English, or Spanish). It covers quickstart, prerequisites, repository structure, GitHub setup, CI/CD, cloud setup, database, deployment, ArgoCD, and troubleshooting.

Code comments and templates are in English (the international standard). The handbook is generated in the language you ordered (German / English / Spanish).

For developer teams and companies that need a professional setup without spending weeks on boilerplate, cloud setup, and CI/CD. The offer is exclusively aimed at entrepreneurs as defined by § 14 BGB (B2B).

Google Cloud Platform (GCP) and Amazon Web Services (AWS). You select at least one provider in the configurator; one cloud is included in the base price. For GCP, Terraform is delivered for GKE, Cloud SQL, Artifact Registry, and Workload Identity. For AWS, for EKS, RDS, ECR, and IAM roles.

Cloud costs are paid directly to your cloud provider — not to us. We deliver the code; hosting runs on your own GCP or AWS account.

You do. Vela Atlas is not a SaaS or hosting offering. Code and cloud resources live in your GitHub and cloud accounts. After delivery, you become the controller within the meaning of the GDPR.

No — if you do not provide a hostname, the application runs on an IP-based address via nip.io. You can configure your own domain at any time later.

Germany, Austria, and all EU countries. We do not sell to Switzerland or other non-EU countries.

Backend: Spring Boot 4.0.6 on Java 25, Spring Cloud 2025.1.1. Frontend: Angular 21 on TypeScript 5.9. Database: PostgreSQL 15 (Cloud SQL or RDS). Migration: Liquibase or Flyway. Container: Jib + Docker. Deployment: Helm + ArgoCD on Kubernetes. CI/CD: GitHub Actions with OIDC. A complete list of all versions is on the versions page.

Yes — all three can be toggled individually in the configurator. The build detects this automatically and delivers only the components you actually need.

Both are supported. Liquibase is the default and works with YAML changelogs. Flyway is classic SQL-based schema management. Pick whichever your team already knows — the generator adapts.

Both are possible. Multi-repo (app, Helm, Terraform, config server each in its own repository) is the default. You can switch to mono-repo in the configurator, putting all components together.

Between 1 and 5 backend services. Service names may be at most 25 characters long. The build duplicates the service template accordingly (own ports, schemas, Docker entries).

At least one is included in the base price (typically: dev). You can define any number of stages, e.g. dev, staging, prod — each gets its own Helm values and config files.

Multi-branch (default): one Git branch per stage (dev/staging/prod) with its own deployment workflow — the classic promotion model. Single-branch: trunk-based development, everything on main, stages distinguished by tags or pipeline parameters.

Yes — the app name may be at most 15 characters long and may contain only lowercase letters and digits. This restriction comes from cloud resource naming (DNS-compliant, AWS/GCP limits).

After payment, you fill in a data form (app name, cloud tokens, service names, optional domain). The build pipeline (GitHub Actions) then generates your personalized repositories from templates, creates them in your GitHub account, stores the cloud tokens as GitHub Secrets, builds the PDF handbook, and reports back "done".

You are notified automatically by email. The most common cause: an expired cloud token (GCP bootstrap tokens are only valid for ~60 minutes). You have a 30-day right to repair — we investigate the error and restart the build at no extra cost. If the build cannot be repaired within this period, we refund the purchase price.

7 days from dispatch. If you miss the download, the link can be reactivated on request — just email support@velaatlas.com.

A GitHub account with a Personal Access Token (for repo creation), cloud account data (GCP project ID + bootstrap token or AWS account ID + bootstrap token), and an app name (max 15 characters). Optional: your own domain. Detailed step-by-step instructions are on the demo page.

Yes — automatically after a successful build, as a PDF by email. On request with VAT ID for the reverse-charge procedure on EU B2B orders outside Germany.

Tokens are passed to the build pipeline encrypted, used only once for repo creation and infrastructure bootstrap, and discarded immediately after the build. Only the configuration remains — no credentials.

Yes. We process only the data necessary for contract conclusion and delivery. For GitHub as data processor (USA), Standard Contractual Clauses under Article 28 GDPR are in place. Details in our privacy policy.

Nobody but you. The repositories created during the build are private and accessible only via your GitHub account. We keep no copy after delivery.

In your own GitHub account and on your own cloud (GCP or AWS) — not with us. Vela Atlas delivers the code as a one-time handoff.

GitHub Actions with OIDC (no password handling), secrets stored as encrypted GitHub Secrets, Workload Identity or IAM roles instead of service account keys (where possible), container builds via Jib (reproducible, no Docker daemon access), TLS via cert-manager + Let's Encrypt.

Credit card via Stripe or PayPal — no other payment methods are accepted. Payment is due with the order; the build starts only after payment is received.

EU B2B customers outside Germany enter their VAT ID at checkout. We validate it live via VIES; with a valid ID, billing is processed under the reverse-charge procedure (without VAT shown). Tax is owed in your home country.

German small businesses can declare this at checkout — billing then proceeds without VAT. Regular German companies pay 19% VAT. Outside the EU, Vela Atlas is not available.

Currently no. Sales are limited to Germany, Austria, and all EU countries.

No. Vela Atlas is a strictly B2B offer under § 14 BGB. Consumers (B2C) are explicitly excluded from the contract — accordingly, the right of withdrawal does not apply.

Yes. You receive the complete source code and a simple, non-transferable right of use for your own purposes. You may use, adapt, and extend the code internally — the exact terms are in T&C § 8 (Right of Use).

No. Passing it on to third parties, uploading to public networks, or commercial resale are excluded. Open source components (Spring Boot, Angular, PostgreSQL, etc.) are subject to their own licenses; complying with them is your responsibility.

Vela Atlas is a one-time delivery — no subscription, no ongoing updates. However, you can order a new build with newer versions at any time.

For technical questions, reach us at support@velaatlas.com. Build errors are covered by the 30-day right to repair; additional consulting or custom adjustments can be commissioned separately.

Warranty for defects is provided under statutory provisions, with a shortened term of 12 months from delivery (B2B standard). Obvious defects must be reported without delay. Details in T&C § 10.