A production-ready UI that validates NextDeploy while serving real users
NextDeploy Frontend is more than a dashboard—it's a living stress test for our deployment platform. Every page load, API call, and user interaction validates NextDeploy's capabilities in real-world conditions.
- 🔍 Real-world validation - Find edge cases before users do
- 📊 Production observability - Monitor actual deployment behavior
- 🚀 Dogfooding excellence - We deploy with what we build
- 📚 Living documentation - UI that reflects current platform state
- Node.js 18+
- pnpm (recommended)
# Clone and install
git clone https://github.com/aynaash/nextdeploy-frontend
cd nextdeploy-frontend
pnpm install
# Start development server
pnpm dev# Install NextDeploy CLI
curl -fsSL https://nextdeploy.one/install.sh | sh
# Deploy this frontend
nextdeploy build && nextdeploy ship| Component | Technology | Purpose | Status |
|---|---|---|---|
| Framework | Next.js 14 (App Router) | SSR/ISR with React Server Components | 🟢 Stable |
| Styling | Tailwind CSS | Utility-first responsive design | 🟢 Stable |
| Database | PostgreSQL + Drizzle | Optional persistent state | 🟡 Optional |
| Real-time | WebSockets | Live deployment logs | 🟡 Improving |
| Auth | Custom RBAC | Route protection & permissions | 🟢 Stable |
graph TB
A[NextDeploy Frontend] --> B[Dashboard UI]
A --> C[Documentation]
A --> D[API Layer]
B --> E[Deployment Management]
B --> F[Environment Config]
B --> G[Real-time Logs]
D --> H[NextDeploy Backend]
D --> I[WebSocket Server]
D --> J[Auth Service]
style A fill:#e1f5fe
style H fill:#f3e5f5
- Deployment Pipeline - Visual deployment status and controls
- Environment Management - Configuration for dev/staging/production
- Real-time Monitoring - Live logs and system health
- Team Collaboration - Multi-user access with role-based permissions
- Interactive Examples - Runnable code samples
- API Reference - Auto-generated from OpenAPI specs
- Best Practices - Battle-tested deployment patterns
- Troubleshooting - Common issues and solutions
Every component tests critical Next.js features in production:
- SSR/ISR Pages → Rendering pipeline stress tests
- API Routes → Backend connectivity validation
- Middleware → Auth and edge logic verification
- WebSocket Connections → Real-time communication stability
nextdeploy-frontend/
├── app/ # Next.js App Router pages
│ ├── dashboard/ # Protected dashboard routes
│ ├── docs/ # Documentation pages
│ └── api/ # API route handlers
├── components/ # Reusable UI components
│ ├── ui/ # Base components (buttons, inputs)
│ ├── dashboard/ # Dashboard-specific components
│ └── docs/ # Documentation components
├── lib/ # Utilities and configurations
├── hooks/ # Custom React hooks
└── types/ # TypeScript definitions
| Route | Purpose | Auth Required |
|---|---|---|
/ |
Landing page with platform overview | No |
/dashboard |
Main deployment interface | Yes |
/docs |
Public documentation | No |
/api/deployments |
Deployment management API | Yes |
/api/logs |
Real-time log streaming | Yes |
# Start with hot reload
pnpm dev
# Run with production build locally
pnpm build && pnpm start
# Run tests
pnpm test
# Type checking
pnpm type-check# Required
NEXTDEPLOY_API_URL=https://api.nextdeploy.one
NEXTAUTH_SECRET=your-secret-key
# Optional
DATABASE_URL=postgresql://...
WEBSOCKET_URL=wss://ws.nextdeploy.oneChoose your platform:
curl -fsSL https://nextdeploy.one/linux-cli.sh | shcurl -fsSL https://nextdeploy.one/mac-cli.sh | sh# Run as Administrator
iwr -useb https://nextdeploy.one/windows.ps1 | iexcurl -fsSL https://nextdeploy.one/nextdeployd.sh | sh💡 Pro tip: Use versioned installs (
/install/v0.1.0.sh) for reproducible environments
We welcome contributions that improve platform observability and user experience.
- Enhance error boundary coverage
- Add deployment health indicators
- Improve real-time status components
- Create additional platform validation tests
- Fork & Branch - Create feature branches from
main - Test Production Scenarios - Ensure changes work when deployed
- Maintain Simplicity - Prefer clear code over clever abstractions
- Add Observability - Components should reveal system behavior
- Does this improve system observability?
- Is the code maintainable at scale?
- Will failures be clear and actionable?
- Have you tested the deployed version?
gantt
title Development Roadmap
dateFormat YYYY-MM-DD
section Core Features
Edge Function Testing :active, 2024-03-01, 30d
Advanced Team Management :2024-04-01, 21d
Multi-region Deployments :2024-04-15, 28d
section Observability
Deployment Health Scores :2024-05-01, 14d
Performance Monitoring :2024-05-15, 21d
Cost Analytics Dashboard :2024-06-01, 14d
- 🌐 Edge Function Testing - Validate serverless functions across regions
- 👥 Team Management 2.0 - Advanced RBAC and collaboration tools
- 📊 Health Scoring - Automated deployment quality assessment
- 💰 Cost Monitoring - Resource usage tracking and optimization
- NextDeploy CLI Repository - Core deployment engine
- Architecture Decisions - Technical design choices
- API Documentation - Complete API reference
- Contributing Guide - Detailed contribution workflow
- Issues - Bug reports and feature requests
- Discussions - Community Q&A
"The interface is the system"
We believe frontend infrastructure isn't just about pixels—it's about creating interfaces that make complex distributed systems understandable, reliable, and delightful to use.
This project embodies our commitment to:
- Production-first development - If it doesn't work deployed, it doesn't work
- Observability through UI - Every component reveals system state
- Simplicity over cleverness - Clear solutions that scale with teams
- Continuous validation - Always testing our own platform
Ready to deploy?