Monorepo structure: apps/core main site, apps/brands brand landing pages, packages/ui shared components
astro-dato-multilaunch — Astro Starter Template
By bejamas
An Astro and DatoCMS multi-brand monorepo launcher template that manages sites for multiple brands, languages, and regions from a single codebase.
Explore the design
Compare the page layouts and mobile experience. Open any screenshot for a closer look.
Actual screenshot captured by the server browser.
All pages & views 3
Screenshots show visual appearance; interactive behavior may differ.
What stands out
A quick read of the recorded project description.
Content driven by DatoCMS, connected via a read-only API token
Supports independent colors and assets for each brand
Supports multilingual content, described in the README as AI-assisted translation
Automatic region-based redirection to show corresponding content to different areas
Built-in light and dark modes
Template Details
This is an Astro monorepo template that uses DatoCMS as its content source to launch and manage websites for multiple brands, languages, and regions from a single codebase. The repository is structured into apps/core (the main retail company page), apps/brands (individual brand landing pages), and packages/ui (shared UI components), with components and configuration shared across brands. The template provides a multi-brand architecture, per-brand custom colors and assets, light and dark modes, multilingual support (the README describes it as AI-assisted translation), and region-based automatic redirection for content delivery. Content and page structure are driven by DatoCMS, so you must first create a DatoCMS account and configure a read-only API token. Local development depends on Node.js and Bun, using scripts such as bun install, bun dev, and bun run build. The README also outlines deployment via Vercel's GitHub integration and initializing the project with DatoCMS's clone button. The template is MIT licensed and free to use, modify, and use commercially, but third-party assets such as demo images, fonts, and icons, as well as external services like DatoCMS and hosting, require separate verification of licensing and costs.
Is it right for your project?
Use Cases
- Build separate landing pages for multiple brands under one company while sharing the same UI components
- Publish localized sites for the same brand or product line across different languages and regions
- Maintain multiple sites centrally in a monorepo to reduce duplicated component and configuration work
- Use DatoCMS as a unified content backend for editors to maintain content for each brand
Suitable For
- Startup teams or mid-sized retailers that need to manage multiple brand sites
- Teams already using or willing to use DatoCMS as their content management system
- Developers familiar with Astro, Bun, and monorepo workflows
Getting started & customization
Use these recorded setup notes alongside the repository instructions for your chosen version.
- 1
First create an account on DatoCMS, and you can initialize the project from this repository using its clone button
- 2
Copy .env.example to .env and fill in the read-only API token from the API tokens in your DatoCMS project settings
- 3
Install Node.js and Bun locally, then run bun install and bun dev to start the development server
- 4
For deployment, refer to the README's method using Vercel's GitHub integration
- 5
Licenses for third-party assets such as demo images, fonts, and icons must be verified separately; external services like DatoCMS may incur costs
License & source material
Usage conditions & limitations
Free to use · keep license noticeThis entry covers the free version under the MIT license in the public repository; the free scope is the code of this version and does not mean external services or third-party assets are free.
Must comply with when using
- You are allowed to use, modify, use commercially, and distribute the code of this version for free.
- When distributing copies or substantial portions of the code, retain the original author's copyright notice and the full MIT license notice.
- The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.
Additional costs & items to verify
- Demo images, fonts, icons, and other third-party assets must be checked under their respective licenses and cannot be judged solely by the code's MIT license.
- External services such as domains, hosting, databases, payments, or AI may incur additional charges.
- You must register an account on DatoCMS before using this template; content management depends on this external service.
- Local operation requires obtaining a read-only API token from the DatoCMS project settings and writing it into .env; without this key, you cannot connect to the content source.
- The local development environment requires both Node.js and Bun; build and run scripts are based on Bun.
- The deployment path given in the README depends on Vercel's GitHub integration, which is an external hosting service.
View Original Text Basis
Permission is hereby granted, free of charge
Original License Text
1. Create an account on DatoCMS
Original README
3. Copy Read-only API token 4. Paste into `.env` file
Original README
- Node.js - Bun
Original README
https://github.com/bejamas/astro-dato-multilaunch/blob/main/LICENSEhttps://github.com/bejamas/astro-dato-multilaunch/blob/main/README.mdDeploy on Vercel with GitHub Integration
Original README
Compiled by DeepSeek based on repository license and README ·2026-10-04. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.
Project checks & description sources
Template Information
- Source platforms
- Astro Themes
- Documentation and maintenance reference score
- More documented · 87 / 100
- Technologies
- Astro
- Website type
- Starter
How this score is calculated
Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.
What to verify for this project
- Repository update recorded
- 2026-08-30
- Screenshot last checked
- 2026-10-04
A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.
The catalog identifies Astro as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.
Use a selection guide →How this description was prepared
AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.
Review declaration: [email protected] · 2026-10-05
Inspect the recorded source material
SHA-256: f408cd3e699e6d8fce343f6d8960ea71d3292535f3fd547aeb445df88f3f591a
2026-10-04T20:29:19.442Z
Source file / repository# MultiLaunch: Astro Multi-Brand Website Template

A high-performance monorepo template built with Astro & DatoCMS for managing multiple brands effortlessly.
Ideal for startups and mid-sized retailers needing a scalable, cost-effective, and multi-language brand hierarchy.
## Demo
[Live Demo](https://astro-dato-multilaunch.vercel.app/en/)
## Tech Stack
- Astro
- DatoCMS
- Tailwind CSS 4
## Features
- ✅ Multi-Brand Architecture – One main site, multiple brand landing pages
- ✅ Rapid Deployment – Add a new brand in minutes, not weeks
- ✅ Monorepo Setup – All brands in one repository for easy management
- ✅ AI-Powered Translation – Multi-language support with AI-assisted translations
- ✅ Geo-Redirects – Serve region-specific content automatically
- ✅ Brand-Specific Customization – Each brand gets its own colors and assets
- ✅ Dark & Light Mode
## Quick Start
1. Create an account on DatoCMS
2. Deploy on Vercel with GitHub Integration
3. Let DatoCMS set up your project:
[](https://dashboard.datocms.com/deploy?repo=bejamas%2Fastro-dato-multilaunch)
## Local Setup
### Prerequisites
- Node.js
- Bun
### Project Structure
```
multilaunch/
├── apps/
│ ├── core/ # Main retail company page
│ └── brands/ # Brand landing pages
└── packages/
└── ui/ # Shared UI components
```
### Getting Started
```bash
# Install dependencies
bun install
# Set up environment variables
cp .env.example .env
```
### Environment Variables
1. Go to DatoCMS project Settings
2. Navigate to API tokens
3. Copy Read-only API token
4. Paste into `.env` file
## Available Scripts
```bash
# Run development server
bun dev
# Build for production
bun run build
# Preview production build
bun run preview
```
## Contributing
Contributions are welcome!
Explore similar templates
Compare previews and descriptions within the same stack and category.

astrowind
AstroWind is a free, open-source Astro starter theme using Astro and Tailwind CSS, released under the MIT license.
Astro · Blog
accessible-astro-starter
An accessibility-focused Astro 6 starter template with WCAG 2.2 AA practices, Tailwind CSS 4, TypeScript, Prettier, ESLint, form validation, blog and portfolio examples, and preference toggles for dark mode, high contrast, and reduced motion.
Astro · Blog

astro-erudite
astro-erudite is an opinionated, unstyled static blog template built with Astro and native CSS, with no UI or CSS framework and minimal dependencies.
Astro · Portfolio

astro-shopify
A lightweight Shopify headless ecommerce starter template built with Astro and Svelte, integrating the Shopify Storefront API for product and inventory data, with built-in cart state management and basic add-to-cart and checkout flow.
Astro · E-commerce

brutal
Brutal is a neobrutalism Astro starter theme from ElianCodes, derived from the author's personal site and generalized. It includes a Markdown blog collection, build-time RSS and sitemap, image optimization, Tailwind CSS styling, and Biome checks, with no JavaScript by default.
Astro · Starter

qwind
Qwind is a free and open-source website template built on Qwik and Tailwind CSS, featuring directory-based routing via QwikCity, a Markdown blog, dark mode, and static deployment configuration.
Astro · Tool Site
