Documentation
Features
How a Nexugen build works, building together in real time with your team, deployment options and custom domains.
How a build works
A build happens in steps. Nexugen first turns your description into a plan, then sets up where your information is stored, makes the pages, adds sign-in where you need it, styles everything to your brand and puts it together. Nexugen chooses the AI for each step, so builds keep working as the technology changes.
The build then checks itself: your app is actually started, and if something is broken Nexugen reads the problem, fixes it and tries again, rather than handing you something that does not work. If your app needs to store information, its storage is set up in the same run.
After the first build, the same machinery serves smaller jobs:
- Edits. One instruction, one session, one redeploy. Edits that pause part way (a usage limit, a restart) can be resumed.
- Proposals. An edit parked for review instead of applied live, shown with a summary of what applying it would change against the current files.
- Agent memory. What the agent has learned about how you build: your corrections and conventions, kept per person and per team, read by every later run (team conventions outrank personal habits). It is editable by hand and any entry can be retired, because it is only trustworthy if you can see and change it. Reads are advisory: a memory problem never fails a build.
- Idea reviews. Before you build, have the idea itself reviewed. The review is kept, and its findings are applied to the requirements when the project is built.
- Scheduled runs. Write a build or edit prompt now and run it later with nobody present. One-shot only, on purpose: build prompts are not idempotent, so a recurring "build the checkout" would rebuild rather than refresh.
- Security scanner, scaling advisory, customer research. Read-only agents that inspect a finished project: find vulnerabilities with evidence, judge whether the architecture will hold as you grow, or research who the customers are. None of them change code.
- Officers. CEO, CFO, CTO and Growth charters that read what the platform already knows about your projects (build history, sessions, deploys, orders, analytics) and report on it. Read-only by construction.
- Workspaces. Coordinated editing across several repositories at once, for products that are more than one codebase. Available on Pro, Business and Enterprise plans.
Real-time collaboration
Every build, edit and deploy is a session, and sessions are shared. Anyone who can see the project sees the same live run: the current phase, the agent's output, the decisions it asks for, and who else is watching. Team collaboration is included from the Pro plan up; members of a team are entitled through the team owner's plan, so an invited colleague does not need a plan of their own.
- Steer a running session with a message; it is applied at the next phase boundary. Answer a decision the agent is waiting on and it continues within seconds. Cancel a run that is going the wrong way.
- Hand off a session to a teammate. They become the assignee: notified, and named on the session. Assignment is not exclusivity; everyone who could already see or steer it still can.
- The project thread is the team's discussion for a project. It is shown alongside the runs so the conversation and the work stay in one place, and
@nexugenmentions fire edits from it. - Roles. A team member is an Owner, Admin, Member or Viewer on a project. Viewers watch. Members act: fire edits, steer, propose. Admins operate: deploy, change environment variables, restore versions, run mobile builds. Owners can do everything, including delete.
- Visibility. A project is Private, shared with your Team, or Public. Public shares the result with the world and nothing else: versions, the thread, proposals and session detail stay with the team, because snapshots can carry configuration and secrets.
- Team memory. A shared agent memory that every teammate's runs read, so a convention set once is followed by everyone.
Deployment options
- Nexugen hosting. Every finished build runs at
your-slug.nexugen.appwith HTTPS, on its own process with its own database. Edits redeploy it. This is the default and needs no setup. - GitHub. Install the GitHub App and Nexugen creates a repository for a project and pushes every change to it, so the code is yours in the place you already keep code. You can also pull a repository's changes back into the project, and import an existing repository as a new project.
- Vercel pipeline. For a web project you want on Vercel: save, push to GitHub, deploy, to a Preview, Staging or Production environment, with optional environment variables and a custom domain on the Vercel side.
- Mobile. Native Android and iOS builds run on Codemagic; when a native build fails, its log is handed to the agent to fix and rebuild. An Expo project can also be exported for the web and hosted by Nexugen. An Expo token for EAS is connected from the mobile project's page.
- Download. Any project, or any saved version of it, as a zip.
Details of each are in the Deployment guide.
Custom domains
Attach a domain you own to a hosted project: add the DNS records Nexugen shows you, click Verify, and HTTPS is issued automatically once the domain resolves to Nexugen. The step-by-step is under Deployment, Custom domains setup.