Documentation

Getting started

What Nexugen is, setting up your account, creating your first project, how the Builder works and a quick start guide.

Introduction to Nexugen

Nexugen turns a plain-language description into a working, deployed product, and keeps changing it after it is live. You describe what you want; agents plan it, write it, build it, fix what fails, deploy it to its own address, and then take your follow-up instructions for as long as the product exists.

There are several ways to start, and they suit different jobs:

  • Build from a prompt (the Builder). Nexugen builds a website, phone app, landing page, online shop, booking system or WordPress plugin from your description. This is the path for something new and specific to you.
  • Instant Apps. Ready-made apps for common businesses (restaurants, stores, booking, real estate, hotels, logistics, job boards and more) that are live in seconds and managed from an admin panel, with their own generated design. You describe the business; Nexugen picks the closest base, brands it and seeds a starter catalogue.
  • Templates. A catalogue of finished apps you own outright once created.
  • Import. Bring a ZIP or a GitHub repository into a project and change it by describing what you want.
  • Legacy upgrade. Point Nexugen at an old codebase and a modern target stack. It writes characterization tests first to lock in current behaviour, then ports and proves parity.

Your account

Sign in with any of:

  • Google or GitHub.
  • An email magic link. The link is valid for 30 minutes and signs you in on the device that opens it.
  • Email and password. Passwords must be at least 8 characters and are stored scrambled, so nobody at Nexugen can read them. A new password account must verify its address first: click the link emailed at sign-up (valid for 24 hours) and then sign in. Reset a password from the sign-in page; a reset link is emailed to you.

A signed-in session lasts 30 days and refreshes as you use it. Signing in with GitHub also lets Nexugen create and push repositories for your projects once you install the GitHub App (Dashboard, GitHub).

Registering an organisation. Tick "I'm registering for an organisation" at sign-up to name it and list colleagues to invite; you become its admin. Team collaboration is included from the Pro plan up (Pro has 3 seats, Business 10, Enterprise as many as you need), so the organisation is saved with your account and its team and invitations are created as soon as one of those plans is active. Until then you have the full single-player product.

Creating your first project

  1. Open New project from the dashboard. Pick what you are building: Web App, Mobile App, Landing Page, SaaS, E-commerce, WordPress Plugin, API / Backend, or Clone Website (rebuild a site from its URL).
  2. Nexugen picks the right technology for you. If you have a developer who prefers a particular one, you can choose it under the advanced options. Phone apps come with the server they need.
  3. Describe the product the way you would to a colleague: who it is for, what it must do, what it must look like, anything it must integrate with. Suggested prompts are there if you want a starting point. Detail here saves rounds later.
  4. Start the build. It runs as a session you can watch live: the plan, each phase (scaffold, database, backend, API routes, auth, components, pages, styling, assembly), the code as it is written, and the terminal.
  5. If the agent needs a decision it pauses with needs input and asks you. Answer in the session and it continues. You can also steer it mid-run; the instruction is applied at the next phase boundary.
  6. When the build finishes it is deployed to Nexugen hosting at your-slug.nexugen.app with HTTPS, and the project shows as Deployed.

Understanding the Builder

The project page is where a project lives after its first build.

  • Preview shows the running app, with desktop, tablet and mobile frames.
  • Code is every file in the project. You can edit a file directly; saving writes it to the project, and can push it to GitHub when the project is connected.
  • Edit is how most change happens: type an instruction and an agent applies it as a new session, rebuilds, and redeploys. On a shared project you can make the edit a proposal instead, parked for review with a change summary before anyone applies it.
  • Thread is the project's team discussion. Mention @nexugen with an instruction and it fires an edit from the thread.
  • Versions are snapshots of the whole project. Take one before a risky change; restoring one snapshots the current state first, so a restore is itself reversible.
  • Environment, Domains and Runtime cover configuration, custom domains and whether the hosted app is awake. See Deployment.

Quick start guide

  1. Sign in. Install the GitHub App if you want your code in a repository you own.
  2. New project, Web App. Describe the product in a paragraph or two.
  3. Watch the session. Answer anything it asks.
  4. Open the preview at your-slug.nexugen.app. Use Edit for the first round of changes, one instruction at a time.
  5. Add a custom domain under Domains when you are ready to show it to the world.

Prefer code? Everything above is also available from your own scripts through the REST API.

NextFeatures