Appearance
Demo
Vantmetry includes a fully self-contained demo that runs everything in a single Docker container. All data stays on your machine. No external services or accounts needed.
What is Demo?
Demo packages the tracker, ingestor, dashboard, and a test error-generation page into one image. It's designed for trying out Vantmetry without any setup:
bash
docker run --rm -p 48043:8080 vantmetry/demoThen visit http://localhost:48043/demo to trigger test errors, and http://localhost:48043/app to view them in the dashboard.
Generating Test Errors
The demo site includes an error generator page to simulate real errors:
- Fire single error: Click "Fire" to throw a typical JavaScript error (TypeError, ReferenceError, etc.)
- PII masking demo: Click "Mask Test" to see how the tracker automatically redacts sensitive data like emails, credit card numbers, and JWTs
- Error burst: Click "Stress Test" to simulate an error spike and trigger the spike detection feature
Errors appear in the dashboard and are grouped on the overview page when viewing a single error.
Limitations
Demo trades features for simplicity. Some parts of the UI are disabled:
| Feature | Status | Reason |
|---|---|---|
| Email signup/login | Disabled | Dashboard is pre-authenticated, no authentication needed |
| Magic link email | Disabled | No email sending in demo |
| Password settings | Disabled | No user account management |
| Account settings | Disabled | Single hardcoded account only |
| API key management | Disabled | Only the demo public key works |
| Project management | Disabled | Single hardcoded project only |
| Multi-user access | Disabled | All users see the same demo account |
| Persistent storage | Limited | Data persists across restarts but is lost if the volume is deleted |
When to Use Demo
Demo is perfect for:
- Learning: No account signup, see Vantmetry working immediately
- Testing: Generate sample errors, explore the dashboard, test spike detection
Demo is not suitable for:
- Production use (no data persistence)
- Sharing across a team (no multi-user, no accounts)
- Storing real error data (reset on restart)
Data Persistence
Error logs are stored in DuckDB and persist across container restarts. Dashboard settings like API keys and project configuration reset on each restart.