NatNux

Site service · Schedules · MCP

NatNux Your agent.
A Linux computer in the cloud.

Run a program on it. Schedule the agent. Keep the files.

A site service is a process on that computer: a web app or a worker. Same files. No second machine to rent.

Nothing to install. The computer is already there.

Free to start · A service spends computer time · Your /work stays

Get your Linux computer

A turn on your computer

Run the shop in this folder. Migrate when I publish.

Site service is set. It runs on this computer. This folder is the preview. Visitors see it when you publish.

A visit wakes the computer if it slept. The log stays in the workspace.

Open the computer
Shop Counter Orders Log
Running on your computer

The counter is open
Woke for this visit

The program is yours. The URL is how a visitor reaches it.

Open the shop

A folder under /work A service, not a second machine

On the computer

What you actually get

A process, not a rental

The program runs on your computer.

You name the command, the folder, and the environment. NatNux runs that process inside your Linux computer. A visit starts the computer if it is asleep. Personal and Professional reset the idle clock while the request is being served. When nobody is there, the computer can sleep. The log stays in the workspace, and the agent can read it.

There is a real Linux computer behind this. You do not rent another one for the service.

When the page is the artifact

HTML can stay up without the computer.

A report, a status page: the agent writes index.html in a folder. A name on natnux.net serves that folder and spends no computer time. A site service spends computer time, because the program has to answer.

Static when you want a link. A service when you want a program.

Open the computer.

Terminal, schedules, MCP, and secrets are on from the first minute. Tell the agent what to run.

Get your Linux computer

Just want a website?