# Yeeted examples: deploy real apps from your coding agent

Yeeted is a hosting platform for AI-built apps. Your coding agent deploys and
manages your app, databases, logs, domains, and rollbacks from the conversation.

Start with the [deployment walkthrough](getting-started.md), then choose an
example below. Each guide explains the actual source, local setup, deployment
shape, verification steps, and limitations. These are learning examples, not
production application templates or published benchmark results.

## Choose an example

| Example | Stack | Data | What you will learn |
| --- | --- | --- | --- |
| [Polling API](poll-fastapi.md) | FastAPI, SQLAlchemy, Alembic | PostgreSQL; SQLite locally | Deploy an API and apply schema migrations |
| [Server-rendered blog](blog-next.md) | Next.js App Router | PostgreSQL; memory locally | Dynamic rendering, build-time data, and revalidation |
| [Notes with a separate frontend](notes-group.md) | React, Vite, Express | PostgreSQL; optional Redis | Deploy a service group and call the API through the web service |
| [URL shortener](shorten-go.md) | Go net/http | PostgreSQL; optional Redis | HTTP services, redirects, and cache behavior |
| [Rails blog API](blog-rails.md) | Rails API | PostgreSQL | Release migrations and Rails request handling |
| [Guestbook](guestbook-php.md) | Plain PHP | PostgreSQL; SQLite locally | Deploy PHP without a framework or Composer |
| [Expiring text pastes](pastebin-sinatra.md) | Sinatra, Rack | PostgreSQL; memory locally | Text APIs and expiry at read time |
| [Java URL shortener](shorten-servlet.md) | Servlet, JSP, Tomcat | Memory | Deploy an existing Dockerfile and WAR |
| [Slug API, Maven](slug-maven.md) | Java 21, Maven (beta) | None | Build a jar from `pom.xml` with no Dockerfile |
| [Slug API, Gradle](slug-gradle.md) | Java 21, Gradle (beta) | None | Build a jar from `build.gradle` with no Dockerfile |
| [Slug API, C#](slug-aspnet.md) | ASP.NET Core minimal API (beta) | None | Publish a .NET project with no Dockerfile |
| [Slug API, Composer](slug-composer.md) | PHP, Composer (beta) | None | Install locked Composer dependencies |
| [Contrast checker, Angular](contrast-angular.md) | Angular (beta) | None | Build an Angular SPA and serve its browser output |
| [Contrast checker, Vue](contrast-vue.md) | Vue, Vite (beta) | None | Build a Vue SPA with deep-link fallback |
| [Contrast checker, Svelte](contrast-svelte.md) | Svelte, Vite (beta) | None | Build a Svelte SPA with deep-link fallback |
| [Palette report, Astro](contrast-astro.md) | Astro static output (beta) | None | Generate a multi-page static site at build time |
| [Orbit Garden](orbit-vanilla.md) | HTML, Canvas, JavaScript modules | None | Deploy a gravity playground and explorable space atlas with no build step |
| [Regex playground](regex-vanilla.md) | HTML, JavaScript modules | None | Static hosting with browser-side logic |
| [Static status page](status-html.md) | HTML, CSS | None | Deploy plain files with no build step |
| [OS package mirror diagnostic](os-matrix.md) | Multi-stage Dockerfile, Python | Build records | Inspect package sources used during a build |
| [Network egress allowed](egress-allowed.md) | Python stdlib, Dockerfile | None | Prove a build can reach www.google.com, declared via `network_access` |
| [Network egress denied](egress-denied.md) | Python stdlib | None | Prove a running app cannot reach www.google.com without a declaration |

Stacks marked beta are detected and built by Yeeted without a Dockerfile,
but their examples are new to the live examples suite described below. They
stay marked beta until that suite has deployed and verified them.

## Verification

Each example includes a deployed smoke script. Some also include unit or
integration tests; the individual guides list exactly what exists. Integration
tests requiring a deployment may skip when no target URL is configured. A skip
does not verify that application.

The platform repository also contains a live examples suite. It deploys
temporary development projects, checks their behavior, and removes them.
Its Redis paths are not covered. Consult an actual CI run for deployment
results; the presence of the suite is not evidence that the latest run passed.

## Source and contributions

These examples and guides are maintained together in Yeeted's platform source.
Website guides are generated from these Markdown files, so corrections can
travel with the example they describe. Preserve the example's source root when
copying it into your own project. See [Yeeted documentation](https://yeeted.ai/docs.html)
for platform features and current access requirements.