Beta Coming soon. This feature is still being built, so names and details may change before it ships.

Headless Ingot (ingot serve)

Headless Ingot runs the full Ingot IDE on your own server, VM or home box, with no desktop and no window. Start it with ingot serve and open the project as Ingot Web from any browser at ingotide.com/w/<id>: the same files, editors, terminals, agents and chat as the desktop app.

  • Same account. You sign in on ingotide.com with your Ingot account, as on the desktop.
  • Same plan. A request from Ingot Web counts exactly like one from the desktop app: the same usage and the same limits.
  • Web project allowance. Each folder you serve is a Web project and uses one of your plan's Web projects (Bronze 3, Silver 5, Gold 7). See Limits and pricing.

Nothing runs in the Ingot cloud for you. The IDE runs on your machine and keeps one outgoing, encrypted connection to the Ingot relay, which forwards your browser to it. You don't open any inbound port.

Download

Get the package for your server from Download › Headless Ingot. The packages are published with each Ingot release, from the same place as the desktop installers. A platform that has no published package yet says Coming with the first release there, with no link.

ServerPackage
Linux x64ingot-server-<version>-linux-x64.tar.gz
Linux arm64ingot-server-<version>-linux-arm64.tar.gz
macOS (Apple Silicon)ingot-server-<version>-mac-arm64.tar.gz
macOS (Intel)ingot-server-<version>-mac-x64.tar.gz
WindowsNo package yet. Use the Linux x64 package under WSL 2.

Each package holds the IDE backend (with its native modules for that OS and architecture), the web frontend, the language plugins and bin/ingot-server. It needs Node.js 22 on the server.

On macOS, if the download is quarantined, run xattr -dr com.apple.quarantine <folder> once.

Quick start

  1. Install the ingot CLI (Node.js 22): npm install -g @ingotide/cli.
  2. Unpack the package, for example into /opt.
  3. In the dashboard, open Publisher › Tokens and create a token with Serve Web projects (ingot serve) (scope web:serve).
  4. Run ingot serve with the project folder:
tar -xzf ingot-server-<version>-linux-x64.tar.gz -C /opt
export INGOT_SERVE_APP=/opt/ingot-server-<version>-linux-x64
export INGOT_WEB_TOKEN=ingot_pub_...
ingot serve ~/shop --name "Shop"
  1. Open the project from Web projects in your dashboard, or at the link ingot serve prints. Sign in with the same account and the full IDE opens.

The project stays online until you stop ingot serve (Ctrl+C). Ingot listens on 127.0.0.1 only (port 3100, or --port); the relay reaches it from the machine itself.

FlagDefault
[folder]The current folder
--port <port>3100 (local only)
--name <name>name in .ingot/web.json, then the folder name
--app <dir>INGOT_SERVE_APP
--token <token>INGOT_WEB_TOKEN, then INGOT_PUBLISH_TOKEN, then ingot login

A project's share settings (default role, preview port, allowed emails, link expiry) come from its .ingot/web.json, as on the desktop.

Unattended publishing

ingot serve starts bin/ingot-server with a few environment variables. You can set them yourself and start bin/ingot-server directly, for example from systemd, without the CLI:

VariableMeaning
INGOT_WEB_PUBLISH1 publishes the folder as a Web project as soon as Ingot starts
INGOT_WEB_PROJECTThe folder to publish
INGOT_WEB_TOKENA publisher token with the web:serve scope
INGOT_WEB_NAMEOptional project name (default: .ingot/web.json, then the folder name)
INGOT_PORTLocal port (default 3100, always on 127.0.0.1)
INGOT_NODEThe Node.js 22 binary, if node on the PATH is another version

Publishing the same folder again from the same machine reuses its Web project; it doesn't take a new slot.

Keep it running with systemd

# /etc/systemd/system/ingot-shop.service
[Unit]
Description=Headless Ingot (shop)
After=network-online.target
Wants=network-online.target

[Service]
User=dev
WorkingDirectory=/home/dev/shop
EnvironmentFile=/etc/ingot/shop.env
ExecStart=/opt/ingot-server/bin/ingot-server /home/dev/shop
Restart=on-failure

[Install]
WantedBy=multi-user.target
# /etc/ingot/shop.env  (sudo chmod 600: only root reads it; systemd passes it to the service)
INGOT_WEB_PUBLISH=1
INGOT_WEB_PROJECT=/home/dev/shop
INGOT_WEB_NAME=Shop
INGOT_WEB_TOKEN=ingot_pub_...
INGOT_PORT=3100

Then sudo systemctl enable --now ingot-shop, and journalctl -u ingot-shop -f for the logs. To use the CLI instead, set INGOT_SERVE_APP and INGOT_WEB_TOKEN in the env file and use ExecStart=/usr/bin/ingot serve /home/dev/shop.

Docker

Docker image: planned. There is no official image yet; use the package with systemd for now.

Security

  • Owner only. Only the account that published a project opens it as the full IDE. Anyone else with a share link gets the view-only viewer at most: no terminal, agents or settings, and no files that look like secrets.
  • Tokens. ingot serve authenticates with a publisher token, like publishing an extension. Give it only the web:serve scope, keep it out of shell history and world-readable files (use EnvironmentFile= with mode 600), and revoke it in Publisher › Tokens if it leaks. Tokens expire.
  • The relay doesn't store code. Code passes through the Ingot relay and is never stored on the Ingot server. The server keeps only the project's name, its share settings and when it was last active.
  • TLS, not end-to-end. Traffic is encrypted in transit with TLS between your server and the relay, and between the relay and your browser. It is not end-to-end encrypted: the relay decrypts it to forward it, and doesn't keep it.
  • Local only. Ingot listens on 127.0.0.1. Don't expose its port; the relay connection is outgoing.
  • Run it as a normal user. The full IDE (terminal and agents included) runs as the service's user, so use an unprivileged account that can reach only what the project needs.
  • Stop at any time. Stop the service, use Stop or Delete on the dashboard, or revoke the token. See Ingot Web security for short-lived access and rate limits.

Troubleshooting

ProblemWhat to do
"The Ingot server build was not found"Point --app or INGOT_SERVE_APP at the unpacked folder (it has lib/backend/main.js).
"Ingot server needs Node.js 22"Install Node.js 22, or set INGOT_NODE to its binary.
The token has no web scopeCreate a token with web:serve under Publisher › Tokens.
"Web projects are all in use"Add an extra project or delete one on Web projects.
The link says offlineCheck that the service runs (systemctl status ingot-shop) and that the machine can reach the internet.
.ts files open as plain textThe language plugins are missing from the package folder; download it again.