nexpress
Self-hosted Next.js CMS with collections, blocks, themes, plugins, TypeScript + Drizzle ORM + PostgreSQL. Owns the app, content lives in Postgres, and admin is included.
Ficha actualizada 22 sept 2026, 18:52 · upstream 22 sept 2026, 18:29 · release sin release detectada
Qué es nexpress
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
NexPress is a self-hosted Content Management System built on Next.js 16 that provides typed PostgreSQL content storage, theming, plugin extensibility, and deployment validation. Unlike black-box CMS platforms, NexPress keeps the application code under your control while offering full admin access through its included scaffold.
The system stores all site content—including collections, posts, media files, user accounts, member roles, jobs, themes, plugins, imports, and settings—in a typed PostgreSQL database backed by Redis for caching. Content is fully portable across deployments via structured exports that preserve relationships, media references, and plugin state without requiring full re-exports.
Admin access is provided through an integrated admin UI with pages, posts, media management, user roles, member authentication, job scheduling, theme configuration, plugin administration, import/export functionality, and site settings. Plugins can contribute typed hooks, routes, pages, blocks, patterns, scheduled tasks, and declarative Admin surfaces that are validated at startup and by a built-in 'plugin doctor' tool.
Themes include built-in options for publications/blogs, community portals, documentation sites, magazines, portfolios, and storefronts, each with distinct layouts and content structures. Themes can be switched via the admin interface or configured programmatically in nexpress.config.ts.
- Publishing a personal blog or newsletter site where you want full control over content structure without platform lock-in
- Running a community forum or portal with member authentication, role-based access, and rich media content
- Building an editorial magazine or publication that requires custom layouts, featured stories, and author attribution
- Creating a portfolio or studio site where you need to showcase work through curated collections and project pages
- Developing a product documentation site with hierarchical navigation, search, and versioned content management
- Running a brand website that needs to integrate payment gateways (Stripe/Toss) while maintaining full control over the frontend
- Self-hosted Next.js application gives you complete ownership of your app's codebase without vendor lock-in
- Typed PostgreSQL content storage with Drizzle ORM enables type-safe schema management and migration workflows
- Built-in theme system provides multiple out-of-the-box themes for publications, communities, documentation, portfolios, and storefronts
- Plugin architecture allows third-party extensions to contribute typed hooks, routes, pages, blocks, patterns, scheduled tasks, and Admin surfaces with validation at startup
- Deployment bridge includes deploy-plan, production doctor, and migration evidence checks before promoting a host environment
- Full content transfer capability preserves collections, relationships, media references, settings, and plugin state during partial exports
- Self-hosted deployment requires manual database setup, Docker orchestration (docker compose), and infrastructure management
- Media storage is not natively supported in production environments; S3-compatible adapters require custom configuration for durable media hosting
- The admin interface is limited to what's included in the scaffold; additional features may require plugin development or external tools
- Plugin contributions are reference-only at this stage, with no guaranteed type safety guarantees across all third-party extensions
- No built-in analytics or traffic monitoring; you must implement your own tracking and reporting solutions
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Deploy NexPress using Docker Compose. Run `pnpm run setup` to initialize the project, configure environment variables (NP_SECRET for secrets, SITE_URL for domain), and start with `docker compose -f docker/docker-compose.yml up -d db`. For production deployment, use the deploy bridge: first create a plan with `pnpm run deploy:plan`, then run `pnpm db:migrate` to apply schema changes. Before promoting to production, always run `pnpm run ops:preflight` which validates environment configuration, storage setup, job dependencies, migrations, and host assumptions in one report. For Vercel hosting, use the deploy bridge with `NP_STORAGE_ADAPTER=s3`, `NP_S3_BUCKET`, and `NP_S3_REGION`; local media storage is required since Vercel's filesystem is ephemeral. Railway or Render offer dashboard-based Docker deployments but still require S3 for durable media storage.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.