AI Workspace
The AI workspace is the center of the product. It gives users a real chat environment with persistent conversations, resumable streams, parallel streaming, stop, retry, regenerate, saved history, chat search, editable titles, chat drafts, file attachments, project aware context, realtime sidebar updates, unseen indicators, and older message pagination.
It is built for the kind of experience people expect from a serious AI product. Messages support Markdown, code blocks, math, Mermaid diagrams, Streamdown rendering, citations, reactions, copy actions, timestamps, model metadata, and human readable tool status labels.
The workspace also connects chats to projects and files, so users can keep context organized instead of starting from an empty prompt every time.
AI Tools
The assistant can use web search with citations, image generation with stored outputs, support ticket lookup and creation, notification preference lookup and updates, and usage counters for monthly chat, search, and image generation limits.
Video generation is intentionally guarded with a refusal path because it is not a supported tool in the current app.
Projects
Users can create, rename, and delete projects. A project can contain chats and source files, and project source files can be uploaded, previewed, paginated, deleted, and injected into AI context.
File Library
The library stores message sources from general chats, including uploaded chat files, long pasted text saved as files, and generated images. Files from project chats and files uploaded directly to a project stay inside that project’s Sources tab instead of the global Library.
Authentication
Authentication is powered by Better Auth. The app includes email and password sign in, Google OAuth, magic links, passkeys, email verification, password reset, welcome email, two factor authentication with backup codes, thirty day sessions, account deactivation, and account reactivation.
Billing
Billing uses Stripe checkout with example flows for monthly subscriptions, yearly subscriptions, and one time payments. Prices are fetched from Stripe price objects on the server by configured price IDs, and purchase access is tracked after checkout and webhook processing.
These Stripe flows are examples, not fixed product rules. You can replace the price IDs, products, plan logic, and access rules to build the pricing model you want in a few minutes, whether that is monthly subscriptions, yearly subscriptions, lifetime access, downloadable product access, paid tiers, or a mix of those options.
Admin
The admin area includes user list management, user stats, roles, activity, purchase status, account status, role edits, user deletion, user impersonation, and magic link sending from the admin UI.
Marketing Site
Spacerr includes public product pages for the landing experience, pricing, checkout, contact, legal pages, blog, not found handling, and error handling.
The public surface also includes sitemap generation, robots configuration, RSS, llms.txt, metadata, Open Graph support, Twitter cards, and structured data.
Blog
The blog includes post listing, article pages, create and edit flows, Tiptap rich editing, cover image upload, SEO keywords, structured data, and read next recommendations.
Transactional email is sent through Resend. The app includes email templates for verification, magic sign in, password reset, welcome email, and contact form handling.
SEO And Discovery
The project includes metadata, canonical URL support, Open Graph tags, Twitter cards, JSON LD structured data, sitemap, robots, RSS feed, llms.txt, and noindex handling for private pages.
Analytics And UX
The app includes PostHog analytics with cookie consent, responsive desktop and mobile layouts, dashboard sidebar, mobile navigation, command menu, toast notifications, smooth scrolling, theme support, and polished loading states.
Developer Experience
The project uses Bun, TypeScript, Next.js App Router, Prisma, Tailwind CSS, TanStack Query, Zustand, Playwright, feature owned tests, route helpers, API route helpers, typed environment modules, and a strict feature ownership structure. Bun is the default package manager, but the application code is not tied to it. If you prefer pnpm, npm, yarn, or another Node package manager, replace the Bun specific commands in package.json with your own equivalents and use your preferred lockfile. The codebase is strongly typed, performance minded, and organized for fast load times, safe changes, polished user experience, and easy extension.