Prompt in plain English
The welcome flow is built around a direct question: what do you want to build?
Paid Product
CodeSplash Vibes abstracts away the messy parts of AI app building and replaces them with a cleaner prompt-to-preview workflow. Under the hood, the codebase still includes a serious hosted platform with auth, billing, plans, custom models, analytics, and admin operations.
Cloud-backed
Product model
The repo includes a desktop app, Express API, NestJS AI gateway, Supabase/Postgres schema, and Stripe billing flows.
Prompt -> preview
Creation loop
Users can start with natural language, stream responses, view the app live, and inspect project history and generated code.
Admin-ready
Business depth
Plans, discounts, operating expenses, model controls, user analytics, and financial trend screens all exist today.
Sign in
The product begins with a clean account flow instead of immediate technical setup.
Sign up
New users can enter through an onboarding flow that feels product-first and approachable.
Start from the home prompt
The product opens on the core question: what do you want to build?
Made for accessibility
The market positioning should stay very simple for end users: describe the app you want, watch it get built, and avoid unnecessary engineering ceremony. The repo supports that story because the heavy lifting lives behind the scenes.
The welcome flow is built around a direct question: what do you want to build?
Vibes keeps the prompt, response, and preview loop visual, which is critical for non-technical trust.
The product does not stop at a single generated output. It already includes project history, chat organization, version views, and generated code access.
The product abstraction is the selling point. Users should not need to understand models, routing, or backend plumbing to get value.
Serious platform underneath
The repo shows that Vibes is already more than a thin UI wrapper. There is real platform depth here, and the website should use that to build confidence without making the experience feel technical.
Account, profile, settings, billing, plan selection, and subscription-aware flows are already productized.
The platform supports curated models and custom model management instead of trapping users in a single provider.
Discounts, friend-and-family access, plan management, and expense tracking all exist today.
Financial trends, user analytics, model analytics, and usage data make the product look credible as a real business platform.
Screenshots
The website now uses every screenshot you added and groups them into the product narratives they best support.
Onboarding and build loop
Vibes has to feel lightweight and approachable. These screens show the path from sign-in to prompt to streamed response to live preview.
The product begins with a clean account flow instead of immediate technical setup.
New users can enter through an onboarding flow that feels product-first and approachable.
The product opens on the core question: what do you want to build?
Natural-language prompting is the center of the Vibes experience.
Users can see what the system is creating instead of waiting on a black-box jump cut.
The preview experience makes the prompt-to-product value proposition instantly tangible.
Apps, chats, versions, and code
The product gets much stronger when users can revisit builds, browse projects, inspect versions, and open the generated code directly.
Users can keep an organized portfolio of generated apps instead of losing work in a single thread.
A more visual project browser helps the product feel accessible to non-technical users.
Prompt history becomes part of the product instead of disappearing after a single session.
Users can revisit previous build directions visually and keep experiments organized.
Each app has a dedicated workspace instead of being trapped in one long conversation.
Generated apps already carry versioning, which makes iteration much more believable for real use.
Users are not locked away from the output. The product lets them inspect the code that was created.
Account, billing, and model controls
These screens prove that the product is more than a demo shell. Users can manage accounts, billing, plans, settings, and the model layer.
Account controls give the product a more polished consumer experience.
Users can configure the product without getting dragged into engineering detail.
Billing flows are already built into the product instead of hand-waved as a future phase.
Model controls make the hosted platform story more credible and flexible.
Users and admins can extend the model layer instead of staying boxed into a single provider.
Subscription plans are a real part of the product, which matters for launch and monetization.
Admin and analytics
The backend and admin surfaces make Vibes look like a product that can actually be operated, priced, analyzed, and grown.
Promotions and access controls are already supported in the admin surface.
The admin tooling supports friend-and-family style access, discounts, and user-specific offers.
Operating-cost visibility helps position Vibes as a real business platform, not a toy.
The product already includes tooling for keeping the platform economics visible.
Analytics reinforce the seriousness of the hosted platform underneath the vibe coding UX.
Usage by model and provider helps the product look operationally mature.
Admin visibility into users and plans supports launch, retention, and pricing decisions.
FAQ
These answers keep the positioning tight and aligned with what the current codebase and screenshots can honestly support.
It is best positioned for people who want the creative upside of AI app building without needing to understand the plumbing. The copy should stay friendly to non-technical founders, operators, creators, and solo builders.
No. The repo already includes a desktop app, hosted APIs, an AI gateway, database schema, billing flows, and admin tooling. The public story should keep the experience simple, but the underlying product depth is real.
Yes. The current product already has apps, chats, versions, and generated-code views, which makes the output feel more trustworthy and easier to iterate on.
Yes. Billing, plans, models, discounts, operating costs, and analytics are already represented in the codebase and screenshots, which makes them fair to market.
Get started
CodeSplash Vibes is available now across Desktop app with hosted cloud platform. The direct release links stay intact here so the existing GitHub artifact flow keeps working.
Portfolio
Each product page still points back to the broader company story so the site can cross-sell the full portfolio instead of isolating every tool.
macOS, Windows, Linux
An all-in-one desktop engineering environment with 19 integrated modes, 15 CLI agent runtimes, Git workflows, code editing, terminals, and supporting product operations in one place.
Desktop app with hosted cloud platform
A cloud-backed vibe coding platform that simplifies app creation for non-technical users while still exposing projects, chats, versions, code, billing, models, and analytics.
Obsidian plugin
A free Obsidian plugin with a visual theme editor, 22 built-in starter themes, live preview, quick switching, import/export, and the transparency effect that gives the vault a more modern feel.
Chrome and Chromium-based browsers
A free browser extension that replaces the boring text-first new tab with a visual home screen built around folders, custom backgrounds, custom icons, drag-and-drop organization, and cleaner everyday access to favorite sites.
Planned for web, mobile, Chrome, and iOS
A planned web and mobile bookmark manager with browser and iOS capture flows, AI summaries, tagging, search, and source-agnostic organization.