Nexus Content is a modern, multi-site content management system built for developers. It provides a centralized platform to manage blog posts, support documentation, FAQs, and legal pages across multiple websites.
Each website gets its own site entry with a unique API key. Documents can be assigned to specific sites or marked as universal (available to all sites). External sites fetch content via our REST API using their API key for authentication.
Nexus Content is currently in beta and free to use. We're exploring pricing models for the future, likely based on API requests and storage usage. Early adopters will receive lifetime discounts.
We're built on Next.js 15 (App Router), Prisma ORM, Neon PostgreSQL, Clerk authentication, and deployed on Vercel. The editor uses TipTap for rich text editing.
API requests are limited to 100 requests per minute per API key. Rate limit info is included in response headers (X-RateLimit-Limit, X-RateLimit-Remaining). Exceeded limits return a 429 status with retry-after guidance.
Yes! Each site entry includes a domain field. You can use any domain you own. The API doesn't validate domains - it's just for identification and documentation purposes.
API responses include CDN-friendly cache headers (Cache-Control: public, s-maxage=300). We cache for 5 minutes with stale-while-revalidate for 10 minutes. This reduces database load while ensuring fresh content.
API keys are hashed with bcrypt before storage. We never store plaintext keys. Keys are shown only once upon creation - save them securely. You can regenerate keys at any time.
Yes! We use PostgreSQL Row-Level Security (RLS) policies. Each user can only access their own documents and sites. Clerk authentication ensures user identity.
Nexus Content provides soft delete functionality, allowing you to recover deleted documents. For permanent deletion (GDPR "right to be forgotten"), use the permanent delete feature. We don't track user behavior or use analytics cookies.