# Introduction

> Streams overview for Laravel developers and teams.

Source: https://streams.dev/docs/introduction

## What is Streams?

Streams is a system of unified Laravel packages that provide an optimized foundation for **data modeling**, **admin interfaces**, **APIs**, and **development workflow**.

Your team defines domain data as JSON stream configurations in `streams/`. Those definitions are version-controlled, reviewable, and shared across environments—the same way you already manage Laravel config and migrations.

> Streams leans on domain-driven design. We call these domain abstractions **streams**.

Working on **this repository**? Start with [This project](/docs/this-project).

## Who it is for

Streams is built for **Laravel developers and teams** shipping real products:

- Custom CMS and content sites
- SaaS backends and tenant admin
- Internal admin and product control panels
- Headless APIs for mobile or SPA clients
- Starter projects and composable addons

You can adopt Core alone or compose **Core + UI + API + SDK + Testing** as your project requires.

## Core packages

| Package | Role |
|---------|------|
| [Streams Core](/docs/core/introduction) | Data modeling, repositories, field types |
| [Streams UI](/docs/ui/introduction) | Control panels, forms, tables, pages |
| [Streams API](/docs/api/introduction) | REST endpoints for stream data |
| [Streams SDK](/docs/sdk/introduction) | Scaffolding and dev workflow |
| [Streams Testing](/docs/testing/introduction) | Test environment and helpers |

## Next steps

- [Installation](/docs/installation) — new or existing Laravel projects
- [Architecture](/docs/architecture) — how the pieces fit together
- [Use cases](/docs/use-cases) — pick a path for your product type
- [Configuration](/docs/configuration) — Laravel config and `streams/` layout

## Community

- [Discord](https://discord.gg/vhz8NZC)
- [GitHub](https://github.com/laravel-streams/streams)
- [Stack Overflow](https://stackoverflow.com/search?q=laravel+streams)