Demo & Testing
Explore the Ever Gauzy Platform through our demo environment or set up your own testing instance.
Online Demo
The official Ever Gauzy demo is available at demo.gauzy.co.
Demo Credentials
| Role | Password | Capabilities | |
|---|---|---|---|
| Super Admin | admin@ever.co | admin | Full system access, all organizations |
| Employee | employee@ever.co | 123456 | Employee view, time tracking, tasks |
Demo Notes
- Demo database resets daily with each deployment from the
developbranch - Demo runs the latest development features (may include experimental functionality)
- Data you enter will be lost on the next deployment cycle
- The demo is intended for exploration only — not for production testing
SaaS Platform
The production SaaS environment is available at app.gauzy.co.
The SaaS platform is currently in Alpha stage. Use it cautiously and expect potential data resets during the alpha period.
Staging Environment
The staging environment is used for pre-release testing:
| Service | URL |
|---|---|
| Staging UI | https://stage.gauzy.co |
| Staging API | https://apistage.gauzy.co |
- Built from the
stagebranch via CI/CD - Used to validate releases before production deployment
- Desktop app pre-releases can be configured to connect to the Stage API
Setting Up a Local Test Environment
Quick Demo with Docker
git clone https://github.com/ever-co/ever-gauzy.git
cd ever-gauzy
docker-compose -f docker-compose.demo.yml up
Open http://localhost:4200 and log in with demo credentials.
Full Test Environment
For a more complete testing setup with PostgreSQL and all infrastructure:
# Start infrastructure services
docker-compose -f docker-compose.infra.yml up -d
# Start API and UI
yarn start
Database Seeding
Initial Seed (Automatic)
On first API start with an empty database, initial seed data is created automatically, including:
- Default Super Admin user (
admin@ever.co) - Default Employee user (
employee@ever.co) - Sample organization with basic configuration
- Default roles and permissions
- Feature flag settings
Manual Seed
Re-seed the database at any time:
# Standard seed (basic data)
yarn seed
# Full demo seed (extensive fake data — ~10 minutes)
yarn seed:all
yarn seed and yarn seed:all will reset your database. Unsafe for production!
Seed Data Contents
The full seed (yarn seed:all) generates:
| Category | Data Generated |
|---|---|
| Users | Admin, employees, candidates with various roles |
| Organizations | Multiple organizations with departments and teams |
| Employees | Employee profiles with skills, rates, and settings |
| Projects | Sample projects with tasks and milestones |
| Time Tracking | Time logs, timesheets, and activity data |
| Financial | Invoices, expenses, payments, income records |
| CRM | Contacts, leads, deals, and pipeline stages |
| HR | Time-off policies, equipment, and employee awards |
Testing the API
Swagger UI
Access the interactive API documentation at:
- Local: http://localhost:3000/swg
- Demo: https://apidemo.gauzy.co/swg
- Production: https://api.gauzy.co/swg
API Documentation
Full API documentation (Compodoc-generated) is available at:
- Demo: https://apidemo.gauzy.co/docs
- Production: https://api.gauzy.co/docs
Testing with cURL
# Login
curl -X POST http://localhost:3000/api/auth/login \
-H "Content-Type: application/json" \
-d '{"email": "admin@ever.co", "password": "admin"}'
# Use the returned token for subsequent requests
curl http://localhost:3000/api/user/me \
-H "Authorization: Bearer YOUR_JWT_TOKEN"
Testing with Postman
- Import the Swagger spec from
http://localhost:3000/swg-json - Set up an environment variable for
baseUrl=http://localhost:3000 - Use the Login endpoint to obtain a JWT token
- Add the token to the Authorization header for all requests