Skip to content
Guide

Quickstart

Create your project, connect the public CLI, and open your app in a cloud sandbox.

Quickstart

Start at the developer console. Create a developer account, create a project, and prepare its cloud sandbox. Wait for the sandbox to be ready before connecting your app. Developer accounts are independent of production workspace subscriptions.

Nexia Core is private server software and is not distributed to developers. Do not clone, download, or request access to Core. You work in your own app directory using the public CLI and documented SDK contracts.

Install and connect

Install Node.js 22 or newer, then install the public CLI:

Code example
Shell
npm install --global @nexia/cli@alpha
nexia login <project-id>

Replace <project-id> with the ID from your project console, or copy its complete command. Open the approval page printed by the CLI, sign in, and approve the displayed code for the correct project. You do not need a GitHub token, private repository access, PHP, or Composer for this static app path.

Create and run your app

Code example
Shell
nexia init my-app
nexia validate my-app
nexia dev my-app

Use a new folder: initialization does not overwrite an existing directory. Keep the terminal running and open the workspace URL printed by nexia dev. In the workspace, connect the local app address shown by the CLI if prompted. Your app opens in a Nexia work tab.

Edit my-app/public/index.html and save. Confirm the change in the work tab; reload the tab if necessary. nexia.json declares your app and screens. Keep credentials out of public files. The local server listens on loopback, normally http://127.0.0.1:4310.

Submit a version

Code example
Shell
nexia validate my-app
nexia deploy my-app

Submission creates an immutable version awaiting review. See the decision and feedback in your project console. To submit changed files, increase the version in nexia.json; different contents cannot reuse an existing version. Approval does not automatically install the app in customer workspaces.

Manage your sandbox and connection

Each developer account can have one active sandbox. It lasts seven days; renewing sets expiry to seven days from that moment. Delete a disposable sandbox before creating a replacement. Deletion removes its data; lifecycle history remains.

Run nexia logout to revoke the CLI connection. Stop the local server with Ctrl+C.

Current scope

The CLI alpha supports static browser apps, local previews inside a cloud workspace, and review submission. It does not provide remote server Functions, platform AI billing, or tenant data access. PHP/React App SDK package contracts are a separate integration path; publishing SDK documentation does not grant access to Core or private packages.

Continue with local development or AI-assisted development. Report a sanitized reproduction at Developer Support.

Verify

Run nexia status and confirm the intended project is connected. Open the workspace from your project console and check the app in its work tab.

Source of truth: docs/developers/content/en/getting-started/quickstart.md