---
title: Examples and Deployment
description: DSAR includes runnable examples for local development, integration
  experiments, and product embedding patterns.
group: guides
---
> ⚠️ **Warning:** **Alpha**
> DSAR is currently in alpha. APIs, package surfaces, configuration, and documentation may change as the project evolves.

DSAR includes runnable examples for local development, integration experiments,
and product embedding patterns.

## Example Catalog

|Example|Purpose|When to use it|
|--|--|--|
|`examples/kitchen-sink`|Full local runtime with SQLite, filesystem artifacts, and walkthrough scripts|Start here when you want broad lifecycle coverage fast|
|`examples/dashboard`|Operator-facing Next.js app|Explore admin and operator flows|
|`examples/subject-portal`|Subject-facing Next.js app|Explore request submission, verification, and appeals|
|`examples/local-storage`|Runtime wired to filesystem storage|Validate local artifact persistence|
|`examples/vercel-storage`|Runtime wired to Vercel Blob plus an upload demo|Validate Blob-backed artifact storage and demo uploads|

## Recommended Local Stack

For the broadest local setup, run:

```sh
bunx turbo run dev --filter=./examples/kitchen-sink --filter=./examples/dashboard --filter=./examples/subject-portal
```

Then use:

* `http://kitchen-sink.localhost:1355/api/v1/status`
* `http://kitchen-sink.localhost:1355/api/v1/spec.json`
* `http://kitchen-sink.localhost:1355/api/v1/docs`
* `http://dashboard.localhost:1355`
* `http://subject-portal.localhost:1355`

## Deployment Patterns

### Self-Hosted Runtime

Embed `@dsar/backend` into your own service, choose a persistence layer, then
register storage, inbound, outbound, and auth integrations as needed.

Start with:

* [Backend Runtime Core](../architecture/backend-runtime-core.md)
* [Integration Guides](../integrations/integrations)

### Server-Side Product Integration

Use `@dsar/node-sdk` or `@dsar/core` from trusted backend code in your product.
This is the preferred shape for dashboards, automation, and subject portals.

### Browser-Facing Portals

Do not expose DSAR machine credentials in the browser. Authenticate the user in
the host app first, then call DSAR from a server action, route handler, or
backend service.

See [Auth Model](../architecture/auth-model.md).

## Infrastructure Scope

This workspace does not currently provide one canonical container or production
infrastructure recipe. The examples are intended as composition references for
runtime wiring, auth boundaries, and storage choices rather than turnkey
production deployment manifests.

See [Testing Acceptance and Parity](../reference/testing/acceptance-and-parity.md).