Senova documentation

Everything you need to go from a sentence to a live app.

Getting started

Senova turns a plain-English description into a working web app — with its database, sign-in, and hosting already wired together. You describe what you want, Senova asks a few clarifying questions, and it builds it.

Create an account with your email or with Sign in with Google. Once you are in, you land on your dashboard: a grid of your projects and a prompt box to start a new one.

Credits. Every account gets a monthly pool of build credits. Each AI action spends credits based on how much work it is: a chat is 1 credit, a quick edit is 3, a complex edit is 8, a full new build is 15, and an agent build is 30. The Free plan includes 25 credits a month with up to 5 builds per day; Pro includes 500 credits; Team includes 2,000. When you run out, your existing projects keep running and your published apps stay live — you just can't run new AI actions until your credits refresh or you upgrade.

Plans. Free ($0), Pro ($29/mo), Team ($79/mo). You can start and ship on Free; move up when a project earns it.

Creating a project

There are three ways to start:

Each project shows up as a card on your dashboard. You can rename a project, search your projects, duplicate one to branch off an idea, and move projects you no longer need to the trash (you can restore them for a limited time before they're permanently removed).

Plan mode

Plan mode lets you agree on what Senova will build before it writes any code. When you describe an app, Senova interviews you — asking about the audience, the key screens, and the data you need — and then drafts a plan: the data model, the pages, and how they connect.

You'll see the plan as a card you can read and refine. Not quite right? Tell Senova what to change in plain language and it updates the plan. When you're happy, click Build this and Senova turns the agreed plan into a working app.

Plan first when the app is non-trivial or you want to lock down the shape before spending a build. Skip straight to building when the idea is small and clear.

Tip: the more specific your answers in the interview (real sections, real fields, real tone), the closer the first build lands to what you meant.

Build mode

During a build you'll see progress stream in: the decisions being made, the files being written, and a live preview when it's ready. A first build produces a complete app — pages, styling, data, and navigation — not a stub.

To keep improving it, just send another message. Every follow-up modifies the existing app: "make the hero darker," "add a testimonials section," "add a status field to bookings." You can stop a generation in progress if you want to change course.

Be specific, one change at a time. Small, clear requests apply more reliably than a paragraph of mixed changes. If you want three things, it's often better to ask for them in three messages.

Editing your app

You can shape your app two ways:

You can also adjust your palette and animations from their own views, and bring in your own images to use across your pages.

Preview

The preview tab shows your app live as you build and edit it. You can navigate between pages inside the preview and check different device sizes to see how it responds.

The preview URL is a private, in-workspace view — it is not your public address. When you're ready for the world to see it, publish (below), which gives you a separate public URL.

Database

Every project has its own built-in database. When you describe your app, Senova creates the tables it needs from your description — you don't write schema by hand.

The Data view lets you browse tables, view and edit rows, and see each table's schema. Power users can run queries in the SQL view. The Users view shows the accounts that sign up inside your app (your app's end users, separate from your Senova account). You also get storage for files and a place to set secrets (environment values your app needs).

Branches & history

Branches let you try a direction without touching your main app. Create a branch, make changes on it, and merge it back to main when you're happy — or throw it away if you're not.

Two kinds of history keep you safe: build history lists every build and edit you've run, and version history lets you see what changed and restore an earlier version if a change didn't land the way you wanted.

Publishing

When your app is ready, open the Publish view. Senova hosts it for you with HTTPS and gives you a public URL of the form /p/your-app. Update a live app any time by publishing again; unpublish to take it offline.

On paid plans you can connect a custom domain. Senova applies sensible security and caching headers for your published app automatically. You can also enable a PWA option so users can install your app.

Your published apps stay online even if your build credits run out — credits only pace how much new AI work you do.

Templates & starting points

If you'd rather start from something designed, browse the template categories and the page-layout gallery. Pick one as a foundation and customize it with chat. There's also a marketplace view and ready-made email templates you can adapt for your app's notifications.

Export & GitHub

Your code is yours. You can download your entire project as a ZIP archive at any time, or connect GitHub and sync your code to a repository you control. The export includes all of your project's files, so you're never locked in.

Troubleshooting & FAQ

My change didn't apply the way I wanted

Be specific and make one change per message. "Change the primary color to forest green" applies more reliably than a paragraph listing five different edits. If a change went wrong, restore the previous version from version history and try again with a tighter request.

The preview looks stale

Use the refresh control on the preview. If you just published, give the public URL a moment to update.

I ran out of credits

Everything you've already built keeps working and your published apps stay live. You only need credits to run new AI actions — wait for your monthly refresh or upgrade your plan.

How do I report a bug?

Email [email protected]. You can also check the changelog for recent changes and system status for live service health.

Ready to build? Start free →