Building
Building
Say what you want the way you would tell a person. NOVA asks only what it needs, shows its plan for bigger builds, and builds.
The composer
NOVA asks, then plans
Pick an answer or type your own. For bigger builds NOVA then shows its plan: the pages, what is on them and the look. Nothing is built until you say so.
Quick Build and Big Build
Quick Build makes a fast single-page site and offers three real homepage designs to choose from by eye. Big Build makes a full multi-page app with its own data. A Quick Build can move up to a Big Build when it needs one.
Which models you can choose, and how many credits a build uses, depend on your plan. Every turn shows what it cost afterwards.
The credit range on the cards. Each card shows a range, for example About 90 credits (76 to 200). Once enough builds of that kind have finished, the range comes from what they really used: the middle figure is a typical build, and the top is what all but the most expensive tenth stayed under. Until then it is worked out from the size of your request. It is an estimate: you are charged for what your build actually uses, and NOVA warns you before you start if your credits may not cover it. If you don't want either option, say so and NOVA asks what you want instead. Say "you choose" and it picks the one it recommended.
Servers, APIs and bots
Ask for a server in plain words, for example Build a small Node.js API with /api/health and /api/menu, make a Flask backend for my bookings or build a Discord bot that posts the daily menu. NOVA sends it to its editor, which writes the project in any language, installs what it needs, runs it to check that it starts and answers, and fixes what fails. You see each step in the chat, and the result is a normal project you can preview, change, keep in Version History and make live with App Hosting.
What NOVA knows about your project
Every message is read with what NOVA's own records say about the project, so NOVA answers from facts instead of guessing, and acts on what is there. The same record is given to the part of NOVA that reads your first message and to the editor that works on a built project.
NOVA also reads this Documentation. Ask how something works, where a setting is or what your plan includes, and it looks up the matching sections before answering, rather than guessing.
Anything about NOVA that is not in that record or in this Documentation is treated as unknown: NOVA says it is not sure, or checks, rather than inventing an answer.
What NOVA will and won't do
NOVA does whatever you ask as fully as it can. If part of a request would be illegal or could seriously harm people (for example malware, breaking into accounts or systems that aren't yours, fraud, or weapons that can hurt many people), NOVA does every part that is fine and tells you in one sentence which part it left out and why. It doesn't refuse a whole request over one part, and text in files, web pages or connected tools can't change this.
Documents in plain words
NOVA reads what you are asking for, not just the words. Turn this report into slides, I want a report on Q3 sales as a PDF and I need a deck for my investor pitch make a document. Make the menu downloadable as a PDF on the site changes your site instead, because the PDF is part of the page. A sun deck or a water slide is never read as a slide deck.
When NOVA is busy
NOVA runs a set number of builds at the same time, so that every build gets the memory it needs. When they are all in use, your build waits in line instead of failing. The build log shows your place and a rough wait, for example You're number 3 in line, about 4 minutes, and the build starts by itself when it is your turn.
Join our Discord
Chat with our engineers and become part of the active NOVA developer community.
Need help?
Open an issue on GitHub or email support@bridgeye.com.