neo

One path from local codebase to live runtime.

neo

Put a local codebase on the internet, keep syncing changes, and control a coherent runtime surface instead of a fragile deployment stack.

01

Public runtime without tunnel sprawl.

Put a local codebase on the internet directly, without turning the problem into a pile of tunnels, DNS hacks, and cloud choreography.

02

Serve after the editor disconnects.

The synced cloud replica stays reachable after the origin machine sleeps, disconnects, or disappears from the network.

03

One identity for MCP and runtime control.

The same credential path authorizes runtime actions and MCP access, so control stays unified instead of splitting across parallel systems.