Guides
Production Operations
Run isplay outside local development with external Postgres, durable artifacts, redaction, and explicit safety policies.
The local npx isplay start path is optimized for development. Production or team use should run explicit infrastructure.
Infrastructure
| Component | Recommendation |
|---|---|
| Postgres | Run managed or self-hosted Postgres and set DATABASE_URL. |
| Artifacts | Mount durable storage or set ISPLAY_ARTIFACTS_DIR to backed-up storage. |
| API | Run @isplay/server behind your normal service controls. |
| CLI/SDK | Set ISPLAY_API_URL in every environment that captures or inspects runs. |
| Projects | Create one project per app/service/customer boundary. |
| Redaction | Configure capture policy in app code before data leaves the process. |
Environment Variables
export DATABASE_URL=postgres://...
export ISPLAY_ARTIFACTS_DIR=/var/lib/isplay/artifacts
export ISPLAY_API_URL=https://isplay.internal.example
export ISPLAY_PROJECT_ID=project_...Operational Safety
- Use
recorded-onlymodel policy andpause-for-fixturetool policy for default investigations. - Do not live replay side-effecting tools in production RCA.
- Classify tools before capture reaches production.
- Keep artifact backups aligned with Postgres backups.
- Treat the artifact store as sensitive evidence storage.
- Review retention rules before capturing regulated data.
Known Current Limits
The local server can enqueue replay and experiment jobs with Graphile Worker, but high-volume asynchronous replay still needs production-grade worker sizing, artifact storage, retry policy, and monitoring.
Verification Commands
npx isplay doctor
npx isplay health
npx isplay projects get "$ISPLAY_PROJECT_ID"
npx isplay runs list --project "$ISPLAY_PROJECT_ID"