Terms and Conditions

for the digital B2B product „Vela Atlas»

§ 1 Scope

(1) These General Terms and Conditions (hereinafter: GTC) apply to all contracts concluded via our website between us, Müller Fullstack Engineering GmbH, represented by Managing Director Stefan Müller, Pappelallee 78/79, 10437 Berlin, e-mail: contact@velaatlas.com, phone: +49 176 80314089 (hereinafter „Provider») and the customer (hereinafter „Customer»).

(2) This offer is directed exclusively at business entities as defined in Section 14 of the German Civil Code (BGB) who, at the time of concluding the contract, are acting in the course of their commercial or self-employed professional activities.

(3) The version of the General Terms and Conditions valid at the time of conclusion of the contract shall apply. The General Terms and Conditions shall also apply to all future business relationships, even if they are not expressly agreed upon again.

(4) Deviating terms and conditions of the Customer shall not be accepted. This shall also apply if the Provider does not expressly object to their inclusion.

§ 2 Description of Services

(1) The subject matter of the contract is the one-time delivery of a configured, automatically generated source code kit for a production-ready cloud infrastructure.

(2) The Customer configures their desired architecture in the configurator on the Provider’s website and enters their cloud account credentials. A few hours after placing the order, the Customer receives ready-to-use repositories and infrastructure in their own GitHub and cloud accounts.

(3) Depending on the configuration, the Customer receives the following services:

• Spring Boot microservices: Between 1 and 5 microservices that are fully coded, documented, and tested.
• Optional Angular frontend: A dedicated service with Material Design, routing, and auth scaffolding.
• Optional PostgreSQL database setup: Automatic schema migration with Liquibase or Flyway.
• Optional Spring Cloud Config Server: Centralized configuration management.
• Helm Charts per Stage: For development, staging, and production environments, depending on the selected configuration.
• Terraform modules: For Google Cloud Platform (GCP) (GKE, Cloud SQL, Artifact Registry, Workload Identity) or Amazon Web Services (AWS) (EKS, RDS, ECR, IAM roles).
• CI/CD pipelines: GitHub Actions workflows for continuous integration and continuous deployment.
• Customized PDF manual: In German, English, or Spanish.

(4) Delivery is available either as a direct push to the Customer’s GitHub account or as a ZIP download for manual upload.

(5) Configuration options include:

• Cloud Provider: Google Cloud Platform (GCP) or Amazon Web Services (AWS) — at least one, one included in the base price.
• Frontend: Angular (optional).
• Configuration server: Spring Cloud Config Server (optional).
• Database: PostgreSQL per service (optional).
• Migration tool: Liquibase or Flyway.
• Deployment Stages: Development, staging, or production environments — at least one, one included in the base price.
• Repository structure: Monorepo or split (each service has its own repo).
• Branching strategy: Multi-branch or single branch.
• Number of backend services: 1 to 5.

(6) The service is provided as a one-time delivery. This is not a subscription, SaaS, or hosting service provided by the Provider. The Customer operates the delivered system exclusively on their own cloud account and in their own GitHub account.

(7) The generated code contains open-source components (Spring Boot, Angular, PostgreSQL, etc.) with their own licenses. Compliance with the license terms is the Customer’s responsibility.

§ 3 Conclusion of Contract

(1) The presentation and promotion of the product on the website do not constitute a binding offer to conclude a purchase contract.

(2) The purchase process is divided into several steps:

1. On the product page, the Customer selects the cloud provider (GCP or AWS), optional components (frontend, DB, config server), migration tool, stages, repository structure, branching, and the number of services.
2. During the checkout process, the Customer provides the following information: company name, first and last name, address, country, e-mail, phone number, VAT ID (required for EU customers outside Germany) or small business confirmation (Germany). The VAT ID is validated in real-time against VIES. By submitting the order by clicking the button „Order with obligation to pay», the Customer submits a legally binding order.
3. After successful payment, the order receives the internal status „awaiting customer data» and the Customer receives an e-mail with a link to the order data form.
4. The Customer enters their technical data, such as app name, GitHub repo owner, GitHub personal access token, backend service names, optional GCP project ID, project number, region, bootstrap token, optional AWS account ID, region, bootstrap token, and optional custom domain (hostname). These tokens are encrypted and passed to the build pipeline (GitHub Actions).
5. The build pipeline receives the configuration and tokens, generates the personalized repositories from templates, creates the repositories directly in the Customer’s GitHub account, stores the cloud tokens as GitHub Actions Secrets in the newly created repositories, generates the personalized PDF manual, and sends a callback to the server: „Build complete». During this process, the order status changes from: „Data received» → „Build in progress» → „Completed» (or „Build failed» in case of issues).
6. After a successful build, the Customer receives an e-mail containing an overview of all repositories created in their GitHub account or a token-based download link for the ZIP file (valid for 7 days; reactivation available upon request after that), as well as an invoice in PDF format.
7. Cloud tokens are discarded immediately after use in the build, and GitHub Personal Access Tokens are discarded after repository creation as well. Only the configuration remains; no login credentials are retained.

(3) A contract is only concluded when the Provider accepts the Customer’s order by means of a declaration of acceptance or by delivering the ordered items.

§ 4 Delivery and Availability

(1) The product is delivered either as a direct push to the Customer’s GitHub account or as a ZIP download.

(2) Delivery takes 1 to 2 hours after the order is placed.

(3) If delivery is not possible at the time of the Customer’s order, the Provider shall notify the Customer of this immediately in the order confirmation. If the product is permanently unavailable, the Provider shall refrain from issuing a declaration of acceptance. In this case, a contract is not concluded.

(4) If the product specified by the Customer in the order is only temporarily unavailable, the Provider will also notify the Customer of this immediately in the order confirmation.

(5) Sales are geographically limited to Germany, Austria, and all EU countries. Sales to Switzerland or other third countries do not take place.

§ 5 Prices and Taxes

(1) All prices are net prices plus the applicable statutory value-added tax.

(2) Customers in Germany are subject to a 19% value-added tax. For EU Customers with a valid VAT ID number, billing is conducted via the reverse-charge procedure.

(3) Cloud costs incurred by the Customer after delivery are to be borne by the Customer.

§ 6 Payment Terms

(1) Payment is accepted exclusively by credit or debit card via the payment service provider Stripe. Other payment methods are not accepted.

(2) Payment is due immediately after the product is configured and the transition from the shopping cart to checkout.

(3) Only after successful payment will the Customer’s remaining information be recorded via the order data form (Execution Form). The build process and delivery of the product will take place only after full payment has been received.

(4) The Provider reserves the right to cancel the order if payment is not successfully completed. In such a case, the Customer will be informed accordingly.

(5) In the event of late payment by the Customer, the Customer must pay the Provider late payment interest per annum at a rate of 9 percentage points above the base interest rate.

(6) The Customer’s obligation to pay late payment interest does not preclude the Provider from claiming further damages resulting from the delay.

§ 7 Retention of Title

Ownership of the delivered product remains with the Provider until full payment has been made.

§ 8 Right of Use

(1) The Customer acquires a simple, non-transferable right of use to the delivered product to use the provided source code files for the purpose of initial commissioning and ongoing development of their own cloud infrastructure.

(2) The Customer is entitled to modify, expand, and adapt the acquired source code files in order to run their own commercial software on them. Use of the source code files within one (1) of the Customer’s own projects is expressly permitted and is in accordance with the purpose of the contract.

(3) The use of the source code files for more than one (1) project requires the purchase of an additional license for each additional project. A project, as defined in these Terms and Conditions, refers to an independent application suite consisting of one or more backend services, possibly a frontend and database, under a common app name, with an independent cloud environment. The deployment of the same project across multiple stages (e.g., Development, Staging, Production) is considered part of a single (1) project.

(4) The Customer is not authorized to reproduce, distribute, make publicly available, upload to other networks (whether for a fee or free of charge), imitate, resell, or use the source code files for any commercial purposes beyond the scope of the contract. In particular, the resale of the kit as such, the public provision of the delivered code package to third parties, the reproduction of the kit for third parties outside the Customer’s own corporate structure, and the imitation of the kit as a competing product are expressly prohibited.

(5) The granting of rights of use to the source code files is subject to the condition precedent of full payment of the agreed purchase price.

§ 9 Customer’s Obligations to Cooperate

(1) The Customer is obligated to provide valid and current cloud tokens. This includes, in particular, GCP bootstrap tokens, which are valid only for a limited period of approximately 60 minutes. If a GCP bootstrap token expires before the build process has started or been completed, the Customer is obligated to provide a new valid token. This also applies to other required tokens, such as AWS access keys and GitHub personal access tokens.

(2) The Customer is responsible for deactivating AWS Access Keys after the successful completion of the build process. Since AWS Access Keys are long-lived, it is recommended to deactivate them after use to minimize security risks.

(3) The Customer assumes responsibility for providing and keeping the technical data in the order data form up to date. This includes, among other things, the app name, GitHub repo owner, GitHub personal access token, backend service names, as well as optional information such as GCP project ID, project number, region, bootstrap token, AWS account ID, region, and custom domain (hostname).

(4) The Customer is responsible for ensuring license compliance for the open-source libraries contained in the generated code, such as Spring Boot, Angular, PostgreSQL, and others. The Provider assumes no liability for any license violations.

(5) Upon delivery of the repositories and cloud resources to the Customer’s account, the Customer becomes the data controller within the meaning of the GDPR. This includes compliance with all data protection regulations and ensuring data security.

(6) Cloud costs incurred by the Customer after the delivery of the repositories and cloud resources are the sole responsibility of the Customer. The Provider is released from any liability for these costs.

(7) The token-based download link for the ZIP file is valid for a period of 7 days. If the Customer does not complete the download within this period, the link can be reactivated upon request.

(8) The Customer is required to provide either a valid VAT ID number or a small business confirmation during the checkout process. The VAT ID number is validated in real-time via the VIES system.

(9) The Customer must ensure that all data provided during the checkout process is correct and complete. This includes, in particular, information regarding the company name, first and last name, address, country, e-mail, and phone number.

(10) The Customer is obligated to immediately inform the Provider of any changes to their contact information, particularly their e-mail address, to ensure smooth communication and access to the purchased services.

§ 10 Warranty and Guarantee

(1) The Provider is liable for material defects in accordance with the applicable statutory provisions.

(2) The warranty period is limited to 12 months from the date of delivery of the product.

(3) The Customer is obligated to inspect the purchased digital product and to notify the Provider of any obvious defects immediately. This also applies to hidden defects discovered later.

(4) An additional warranty applies to products delivered by the Provider only if it was expressly stated in the order confirmation for the respective item.

(5) The Customer is advised that the automated build process may fail, for example due to invalid or expired tokens or due to outages at third-party providers such as GitHub. In such cases, the Customer has a 30-day right to have the issue resolved by the Provider. If the build cannot be resolved within this period, the Customer is entitled to a refund.

§ 11 Liability

(1) Claims by the Customer for damages are excluded. Excluded from this are claims for damages by the Customer arising from injury to life, limb, or health, or from the breach of material contractual obligations (cardinal obligations), as well as liability for other damages resulting from an intentional or grossly negligent breach of duty by the Provider, its legal representatives, or vicarious agents. Essential contractual obligations are those whose fulfillment is necessary to achieve the purpose of the contract.

(2) In the event of a breach of material contractual obligations, the Provider shall be liable only for foreseeable damages typical for this type of contract if such damages were caused by simple negligence, unless the claims for damages by the Customer arise from injury to life, limb, or health.

(3) The limitations in paragraphs (1) and (2) also apply in favor of the Provider’s legal representatives and vicarious agents if claims are asserted directly against them.

(4) The limitations of liability arising from paragraphs (1) and (2) do not apply if the Provider has fraudulently concealed the defect or has assumed a guarantee for the quality of the item. The same applies if the Provider and the Customer have entered into an agreement regarding the quality of the item. The provisions of the Product Liability Act remain unaffected.

(5) The Provider assumes no liability for damages resulting from the provision or use of invalid or expired cloud tokens. The Customer is responsible for ensuring that the provided tokens are up-to-date and valid. This includes, in particular, GCP bootstrap tokens, AWS access keys, and GitHub personal access tokens.

(6) The Provider is not liable for damages resulting from the failure to deactivate AWS Access Keys after the build process.

(7) The Provider assumes no liability for build errors caused by invalid or expired tokens, GitHub outages, or other technical issues.

(8) The Provider is not liable for cloud costs incurred by the Customer after the delivery of the repositories and cloud resources. These costs are the sole responsibility of the Customer.

(9) The Provider assumes no liability for license violations arising from the use of open-source libraries contained in the generated code. The Customer is responsible for compliance with the applicable license terms.

(10) The Provider is not liable for compliance with GDPR regulations in connection with the cloud resources and repositories provided and used by the Customer. Upon delivery of the resources, the Customer becomes the data controller within the meaning of the GDPR.

(11) The Provider assumes no liability for damages resulting from the use of the token-based download link, particularly if the download link is not used in a timely manner after the 7-day validity period has expired.

(12) The Provider is not liable for damages resulting from incorrect or incomplete information provided by the Customer during the checkout process, particularly regarding the VAT ID number or the small business confirmation.

(13) The statute of limitations for the Customer’s claims for damages is one year, beginning upon knowledge of the damage and the identity of the party responsible, unless the claims arise from injury to life, limb, or health, or from intentional or grossly negligent breaches of duty. In such cases, the statutory limitation periods apply.

§ 12 Data Protection

Customers can find detailed information on data protection, in particular regarding the scope of customer data processing and their legal rights, in the Provider’s Privacy Policy.

§ 13 Copyrights

The Provider holds the copyrights to all images, videos, and texts published in the online store. Use of the images, videos, and texts is not permitted without the Provider’s express consent.

§ 14 Governing Law and Jurisdiction

(1) Amendments to the Terms and Conditions as well as ancillary agreements must be made in text form.

(2) The law of the Federal Republic of Germany applies, excluding the UN Convention on Contracts for the International Sale of Goods.

(3) The exclusive place of jurisdiction, to the extent permitted by law, is the Provider’s registered office.

(4) Should parts of these Terms and Conditions be wholly or partially invalid, the validity of the remaining provisions remains unaffected. In such a case, the parties undertake to replace the invalid provision with one that largely corresponds to the purpose of the contract and is valid.

(5) The German version of these Terms and Conditions is binding. Translations into other languages are for informational purposes only.

As of: 11.05.2026