Use one workspace for AI chat, app prompts, image, music, video, 3D tasks, credits, and billing. Sign in to start in the chat workspace.
Local demo flows can run with mock-ai and mock-payment.
Creators use newai to keep AI work organized.

newai is built with the current AI SaaS stack
newai brings the GeekAI-style left navigation workspace onto the existing Next.js foundation, so core AI work does not live on the marketing page.
After sign-in, users land in /chat and move through chat, apps, media tasks, credits, and settings from the sidebar.
AI calls are prepared for provider, model, key pool, mock-ai, and future credit settlement paths.
Member plans, power logs, and media task costs stay visible from the workspace instead of scattered landing widgets.
RBAC, audit logs, provider management, and migration dry-run outputs stay connected to the same product surface.
The first version focuses on a usable local demo and a clean path from marketing to the authenticated workspace.
The public home page explains the product; the workspace handles real AI operations.
Start from the marketing page or pricing CTA. The auth flow returns to /chat by default.
Use the default workspace entry for AI conversation and session history.
Move through AI apps, image, music, video, Jimeng, and 3D task pages from the sidebar.
Use member plans, power logs, gallery, invite, and profile pages to complete the user loop.
Core pages stay discoverable from the marketing site, while authenticated actions happen inside the workspace.
Chat, session history, role-style apps, and prompt helpers share the workspace route group.
MJ, SD, DALL-E, and Jimeng entries are reserved for first-version media workflows.
Suno, video, and 3D hand-board style generation fit the unified media task model.
Generated outputs can be reviewed through gallery and storage-backed asset pages.
Recharge, subscription rights, and power logs remain visible from the user workspace.
Provider, model, key, RBAC, audit, and old-system dry-run tools stay in the admin path.
Designed for the first local demo and later production hardening.
Workspace entries
Media modes
Unified sidebar
The first version is shaped around repeatable AI creation flows.
Users can start in /chat, continue sessions, and later select role-style apps without leaving the workspace.
AI chat workflow
Conversation and history
Creative tasks use a shared navigation model, making generated outputs easier to find and review.
Media workflow
Image, music, video, and 3D
Recharge, balance changes, and power logs stay close to the features that consume credits.
Billing workflow
Credits and member plans
Operational pages keep provider catalogs, key pools, and audit evidence separated from user content.
Admin workflow
RBAC, audit, and providers
Old GeekAI data is inspected with dry-run outputs before any protected apply path is considered.
Migration workflow
Dry-run first
mock-ai and mock-payment keep the first version testable before real provider and merchant accounts are configured.
Local demo workflow
Mock providers
Key product and local-demo decisions for the first version.
Use the public site to understand the product, then sign in to create from /chat.