ESEN
ESEN

Codex VPS

Codex VPS: the repetitive work, running by itself on your server

One command installs Codex on Ubuntu 24.04 and it stays on the server: by hand inside a tmux session while you work, or in non-interactive mode when you want a task to repeat with nobody watching.

The short answer

Codex is OpenAI’s console agent and a single command installs it on a Linux VPS. On a server the device-code sign-in is the one to use, since there is no browser; from there you run it in two ways: interactively inside tmux, or through codex exec for one-shot tasks you can call from a script or from cron. At SISArgentina the VPS comes with Ubuntu 24.04 LTS, root access and a static Argentine IP in our Buenos Aires datacenter; the ChatGPT subscription or OpenAI API key is yours to bring. The VM3 plan is the starting point.

  • Codex CLI
  • codex exec
  • Ubuntu 24.04 LTS
  • tmux
  • SSH
  • Git 2.23+
  • cron
  • systemd
  • Docker
  • npm

What you get

The repeats, without your computer on

Non-interactive mode runs one task and prints the result to standard output: bump dependencies on Mondays, go over the day’s commits, draft the notes for a release. Call it from a script or from cron and the server does it at the hour you set.

Explicit permissions, not blind trust

In non-interactive mode Codex is read-only unless you say otherwise: to let it edit files you pass --sandbox workspace-write. You decide the scope, one task at a time.

You sign in even with no browser on the server

The device-code sign-in saves you from tunnelling the callback over SSH: run the command, open the link in your own browser and type the one-time code.

One place for the whole team

The repository, the dependencies and the scripts live on the server, not across five different laptops. Everyone logs in over SSH with their own user and finds the same environment.

A fixed cost on the server side

You pay for the VPS plan and nothing else: we charge no per-task or per-minute fee. Whatever the model consumes is billed by your own OpenAI account, under the same limits you would have locally.

Codex VPS plans

These are the usual Cloud VPS plans, and the cart opens with the system already selected. Monthly prices, final price. USD amounts are the official store list; local invoicing is issued in pesos.

VM1

Sold out

$ 13,455/ mo

  • 1 vCPU
  • 1 GB RAM
  • 15 GB SSD
  • 1 static public IP
  • Unmetered transfer (fair use)
  • Windows or Linux
  • Physical location: Argentina
Check availability — VM1

VM2

$ 26,910/ mo

  • 2 vCPU
  • 2 GB RAM
  • 30 GB storage
  • 1 static public IP
  • Unmetered transfer (fair use)
  • Windows or Linux
  • Physical location: Argentina
Order now — VM2

VM3

$ 40,365/ mo

  • 3 vCPU
  • 3 GB RAM
  • 45 GB storage
  • 1 static public IP
  • Unmetered transfer (fair use)
  • Windows or Linux
  • Physical location: Argentina
Order now — VM3

Most chosen

VM4

$ 53,820/ mo

  • 4 vCPU
  • 4 GB RAM
  • 60 GB storage
  • 1 static public IP
  • Unmetered transfer (fair use)
  • Windows or Linux
  • Physical location: Argentina
Order now — VM4

Codex running in four steps

  1. Prepare the server

    Log in as root with the IP and password you receive by email. Codex asks for Ubuntu 20.04 or later —the VPS ships 24.04 LTS— and recommends Git 2.23 or newer for its pull request helpers; tmux is what keeps the session alive.

    apt update && apt install -y curl git tmux
  2. Install Codex

    OpenAI’s official installer for Linux. The same command updates it later on; if you prefer npm, the package is @openai/codex.

    curl -fsSL https://chatgpt.com/codex/install.sh | sh
  3. Sign in with your account

    The device-code sign-in is meant for machines without a browser: open the link from your own computer, type the code and the session stays on the VPS. You enable it first in your ChatGPT account security settings or in the workspace permissions. Going the API key route instead: printenv OPENAI_API_KEY | codex login --with-api-key.

    codex login --device-auth
  4. Leave it working

    Inside tmux you run codex to work by hand, or codex exec "bump the dependencies and run the tests" for a one-shot task. Ctrl+b d drops the session and tmux attach -t codex brings it back later, from whatever machine you have.

    tmux new -A -s codex

Read on: Snapshots y backups en un VPS: la diferencia que salva · Qué es un VPS y cuándo conviene dar el salto

Frequently asked questions

Do I need a ChatGPT subscription or an API key?

One or the other, and you bring it. Codex runs on a ChatGPT Plus, Pro, Business, Edu or Enterprise account, or on an OpenAI API key billed separately by usage. Our side of the deal is the infrastructure; the agent account is yours and leaves with you.

How do I sign in on a server with no desktop?

With codex login --device-auth, which is in beta and has to be enabled beforehand in your ChatGPT account security settings or in the workspace permissions. If it is not available to you, the documented alternative is copying ~/.codex/auth.json from a machine where the browser flow did work. Treat that file like a password: it holds your access tokens.

Can I schedule tasks with nobody connected?

Yes: codex exec runs a task without opening the interface and writes the result to standard output, so it fits in a script, a repository hook or a cron job on the server. It is read-only by default; to let it modify files you pass --sandbox workspace-write.

Which plan do I need?

OpenAI asks for 4 GB of RAM as a minimum and recommends 8 for Codex. The VM4 (4 vCPU, 4 GB) meets that minimum, and the SH2 cloud server (4 cores, 6 GB) gets close to the recommendation if the same box also runs the database and the tests; the VM3 is where you start when it is only the repository and the agent. Moving up a plan needs no migration or reinstall.

Where do my code and credentials live?

On the VPS, in our datacenter in Chacarita, Buenos Aires, with root access that is only yours. What gets sent to the model is decided by your account and your Codex configuration, not by us. Before letting the agent edit a repository, keep the day’s snapshot: it is the cheapest undo button there is.

Is the server managed?

No. VPS plans and cloud servers are delivered unmanaged: we provide the server with a clean operating system, the static IP and root access, and from there on installing, configuring, updating, securing and backing it up are yours. The commands on this page are the ones in the tool’s official documentation, verified on Ubuntu 24.04, and they are enough to get it running; support for the tool itself is its own documentation and community. If you get stuck with something on the server, write to us and we will lend a hand. And if you would rather not deal with it, our software factory builds custom work on this same infrastructure. Shared hosting with a control panel is a different story: that one we do install and maintain.

Keep going