NEO AppAcme Inc
Portal, CLI, and MCP share the same project state and approval policy.

Docs

How-to guides for deploying and running apps on NEO App.

Documentation

Explore the complete NEO App documentation

Find detailed service, API, CLI, MCP, security, and operations guidance.

Read full documentation
Quickstart

Connect your coding agent

Set up Codex or another MCP client, verify the connection, and deploy without leaving your project context.

~2 min
1
Setup

Paste this instruction into your coding agent. It will fetch the maintained setup guide and stop when your API key is needed.

Fetch https://portal.neoapp.biznetgio.dev/prompt.md and follow it to set this repo up on NEO App.
2
Verify

Restart the agent, then ask it to check CLI status and MCP identity.

Check my NEO App setup: run neo-app status and call neo_whoami. Confirm the organization, project, and environment before changing anything.
3
Deploy

Hand the task to the agent. Project roles and production approval policy still apply.

Deploy the source in this directory to NEO App Production. Inspect first, show the exact plan and hourly IDR estimate, and wait for my approval before applying it. Then verify readiness and the public endpoint.
Getting started

Deploy your first web app

  1. 1
    Create a project

    Projects group services, managed resources, and isolated environments.

  2. 2
    Deploy from source

    Connect Git, upload a ZIP, use a template, or deploy from the CLI and an AI agent.

  3. 3
    Open the live URL

    Web and static services receive a NEO App URL with automatic TLS.

  4. 4
    Review the rollout

    Follow build output, health checks, deployments, logs, and approvals from one workspace.

Read full guide
Configuration

Environment variables and secrets

  1. 1
    Set variables

    Add plain configuration in the service Variables tab or pass it during deployment.

  2. 2
    Protect secrets

    Mark sensitive values as secrets so they are encrypted and masked in the Portal.

  3. 3
    Scope by environment

    Production and staging keep separate values and deployment history.

  4. 4
    Audit changes

    Variable changes follow role policy and appear in Activity.

Read full guide
Data

Managed databases and storage

  1. 1
    Provision a resource

    Create PostgreSQL or Object Storage from Add service in the target environment.

  2. 2
    Bind your service

    Use the generated internal connection details from services in the same project.

  3. 3
    Plan capacity

    Review storage and estimated usage before provisioning.

  4. 4
    Control exposure

    Keep resources private by default and request approval for public endpoints.

Read full guide
Background work

Queues, workers, and scheduled jobs

  1. 1
    Create a NEO Queue

    Use durable message delivery with retention, retry, and dead-letter behavior.

  2. 2
    Run a worker

    Deploy background compute without a public port and bind it to a queue.

  3. 3
    Schedule a job

    Use NEO Cron for a managed schedule, retries, run history, and logs.

  4. 4
    Operate safely

    Trigger runs, inspect failures, and route production changes through Approvals.

Read full guide
Networking

Domains and TLS

  1. 1
    Use the default domain

    Every public web service receives an HTTPS endpoint automatically.

  2. 2
    Add a custom domain

    Attach a domain from Networking and apply the displayed DNS record.

  3. 3
    Verify TLS

    Managed certificates are issued and renewed after DNS validation.

  4. 4
    Keep private traffic private

    Internal addresses remain reachable only inside the project environment.

Read full guide
Billing

Usage and billing

  1. 1
    Review estimates

    Add service shows an estimate that responds to the selected runtime configuration.

  2. 2
    Track actual usage

    Usage groups costs by month, project, environment, and resource.

  3. 3
    Export data

    Download the current dummy ledger as CSV for cost analysis.

  4. 4
    Manage billing

    Open invoices and payment management from the Usage page.

Read full guide
Automation

Keep working with the same project state

Portal, CLI, API, and MCP use the same environments, approvals, logs, and usage records.