Prompt in plain English
The welcome flow is built around a direct question: what do you want to build?
Paid vibe coding product
Paid Product
CodeSplash Vibes
Prompt in English and ship beautiful apps without the technical overhead
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.
Plain-English promptingLive preview and generated code accessHosted auth, billing, plans, models, analytics, and admin tooling
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
A vibe coding product with the complexity hidden in the right places
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.
Streamed responses and live preview
Vibes keeps the prompt, response, and preview loop visual, which is critical for non-technical trust.
Apps, chats, versions, and code
The product does not stop at a single generated output. It already includes project history, chat organization, version views, and generated code access.
Designed to feel effortless
The product abstraction is the selling point. Users should not need to understand models, routing, or backend plumbing to get value.
Serious platform underneath
Not just a prompt toy
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.
Hosted auth and billing
Account, profile, settings, billing, plan selection, and subscription-aware flows are already productized.
Model management
The platform supports curated models and custom model management instead of trapping users in a single provider.
Admin operations
Discounts, friend-and-family access, plan management, and expense tracking all exist today.
Analytics and usage visibility
Financial trends, user analytics, model analytics, and usage data make the product look credible as a real business platform.
Screenshots
Every screenshot connected to a real story
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.
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?
Describe the app in English
Natural-language prompting is the center of the Vibes experience.
Stream structured responses
Users can see what the system is creating instead of waiting on a black-box jump cut.
See the app live
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.
Apps in list view
Users can keep an organized portfolio of generated apps instead of losing work in a single thread.
Apps in grid view
A more visual project browser helps the product feel accessible to non-technical users.
Chat history in list view
Prompt history becomes part of the product instead of disappearing after a single session.
Chat history in grid view
Users can revisit previous build directions visually and keep experiments organized.
Project workspace
Each app has a dedicated workspace instead of being trapped in one long conversation.
Version history
Generated apps already carry versioning, which makes iteration much more believable for real use.
Generated code access
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.
Profile management
Account controls give the product a more polished consumer experience.
Settings
Users can configure the product without getting dragged into engineering detail.
Billing
Billing flows are already built into the product instead of hand-waved as a future phase.
Model selection
Model controls make the hosted platform story more credible and flexible.
Add custom models
Users and admins can extend the model layer instead of staying boxed into a single provider.
Plan management
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.
Discount management
Promotions and access controls are already supported in the admin surface.
Grant access and promotions
The admin tooling supports friend-and-family style access, discounts, and user-specific offers.
Expense tracking
Operating-cost visibility helps position Vibes as a real business platform, not a toy.
Add infrastructure expenses
The product already includes tooling for keeping the platform economics visible.
Financial trends dashboard
Analytics reinforce the seriousness of the hosted platform underneath the vibe coding UX.
Model analytics
Usage by model and provider helps the product look operationally mature.
User analytics
Admin visibility into users and plans supports launch, retention, and pricing decisions.
FAQ
Questions about CodeSplash Vibes
These answers keep the positioning tight and aligned with what the current codebase and screenshots can honestly support.
Who is CodeSplash Vibes for?
CodeSplash Vibes is for founders, creators, operators, and solo builders who want to create apps by describing what they need in plain English.
Do I need to know how to code to use Vibes?
No. Vibes is designed around a prompt-to-preview workflow, so you can start with an idea, review what is generated, and iterate without managing the technical setup yourself.
Can I keep working on a project after the first generation?
Yes. Projects are organized so you can continue conversations, review versions, inspect generated output when needed, and keep refining the app over time.
Is Vibes only for quick prototypes?
Vibes is useful for fast prototypes, but it is also built for projects that need to grow beyond the first draft, with project history and platform controls that support ongoing work.
Get started
Launch CodeSplash Vibes
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.
macOS (Apple Silicon)macOS (Intel)WindowsLinux x64 (DEB)Linux x64 (RPM)Linux ARM (DEB)Linux ARM (RPM)
Plain-English promptingLive preview and generated code accessHosted auth, billing, plans, models, analytics, and admin tooling