Skip to Content

Compute

VMs for agents and apps, and machines for one task.

A VM is a server your Sunport manages, for an agent or your own apps. An environment is a machine for one task, yours or an agent's.

Use it when
An agent or an app needs a server, or a task needs a machine for a while
You get
VMs your Sunport manages, with domains and access you control
Cost
A VM's monthly price, or Included on OpenOrange capacity; environments by use
Setup time
A few minutes for a new VM
Needs
See machines to look; Manage machines and Start jobs to change; Request environments for an environment

Machines

Compute opens on Machines, every server your Sunport uses:

  • Sunport: the server your Sunport runs on. You can't change it here.
  • Agent VM: the VM an agent runs on. New agent creates it; deleting the agent deletes it.
  • Service VM: a VM for your own apps and tools. New VM creates it with Debian 13 and nothing else.
  • Edge gateway: a paid server in front of your Sunport's web and model calls.

External marks a server OpenOrange doesn't manage. It can't be powered, resized or removed from here.

Providers and sizes

A VM runs on a provider you choose when you create it:

  • OpenOrange capacity uses servers OpenOrange already runs. Its sizes show Included.
  • Any other provider, such as Hetzner, rents a new server at its monthly price.
  • On OpenOrange capacity, No public IP keeps a VM private. It can't take domains then.
  • Clem manages this VM lets Clem and administrators work on it as root. Off, only an owner SSH key signs in.

Resizing depends on the provider:

  • On OpenOrange capacity, more CPUs and memory arrive while the VM runs. Less memory needs a short restart.
  • On Hetzner, the VM is off for one to three minutes.
  • On other providers, VMs aren't resized. Move the work to a new VM.

Disks grow and never shrink. A volume is an extra disk on OpenOrange capacity, for data that grows.

What it costs

Machines shows each VM's hours this month, with its price at list price.

  • A powered-off VM is still charged at the same rate. Only deleting it stops the charges.
  • A volume costs a price per GB each month, attached or not.
  • An edge gateway costs its size's monthly price until you remove it.
  • Your server budget caps what servers may cost a month. A new server past it is refused.
  • VMs on OpenOrange capacity have no list price yet, so they don't count toward the budget.
  • Team limits cap how many VMs and published names you have at once.

Who can do what

Each action takes a permission:

  • See machines (hosts.read) shows machines, VM plans and domains.
  • Manage machines (hosts.manage) with Start jobs (jobs.create) plans, powers, resizes and deletes VMs, and changes domains.
  • Only administrators create a planned VM, open a VM's page, and see what machines cost.
  • An agent's owner works as root on that agent's VM, with oo vm shell --agent.

Access for agents

Administrators run commands on any VM without asking. Agents need a grant:

  • Read only: status and logs.
  • Root: any command as root.

An agent asks, and an administrator approves on the VM's Access tab. A requested grant expires. Any grant can be revoked any time. An agent works on its own VM as its own user without a grant. Root there needs one. Clem needs one, unless its VM was made with Clem managing it.

Domains

Domains & routes gives an app on a VM a public HTTPS address. It connects one of three ways:

  • Through Sunport: one port of the VM, at a name under your Sunport's domain. It can ask for the OpenOrange sign-in.
  • Through edge gateway: any name you own. You add its DNS records, and the app keeps its own login.
  • Direct to VM: a name under your Sunport's domain, pointing at the VM. The app serves its own certificate and login.

Routes to servers forwards a name on your own edge gateway to any server by its address.

Machines people share

A service VM or an agent's VM can become a machine that people work on together. Everyone on it works as one Linux account, so they can read and change what is on it. Machines explains who works on one, and what agents may run there.

Environments

An environment is a Linux or macOS machine from Namespace, for one task: yours, or an agent's.

  • It starts from a profile: a machine shape, how long it may run, and what happens to its data.
  • On OpenOrange machines, it is paid from your team balance. It reserves funds upfront, then settles to actual use.
  • On your own Namespace workspace, Namespace bills it.
  • On-demand stops after 15 minutes idle or at its deadline. Without kept data, it is deleted.
  • Keep running until deadline keeps it running while idle.
  • Administrators can set Spending caps per member or agent. Caps never grant permission.

Limits

  • On a free trial, a new VM on OpenOrange capacity has at most 4 vCPU, 8 GB RAM and 60 GB disk.
  • Some sizes are set up by support only.
  • Deleting a VM deletes its data. No backup is taken.
  • Volumes aren't in backups or pre-update snapshots.
  • VMs on OpenOrange capacity can't send mail over SMTP ports 25, 465 and 587. Use a mail provider's HTTPS API.
  • Edge and direct routes have no OpenOrange sign-in.
  • An environment's runs, files and terminal work only while it runs. They never start it.
  • On macOS environments, typed characters don't arrive yet. Clicks and Command shortcuts do.
  • Snapshots, restores, clones and pools work only on your own Namespace workspace.

How-to guides

How-to guides

Create a service VM

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs. In the dashboard, only an administrator creates the VM.

  1. Open Compute and choose New VM.
  2. Fill in Name and Purpose.
  3. Choose a Provider, a Location / capacity node and a Capacity.
  4. Keep Clem manages this VM on, so Clem and administrators can work on it.
  5. To publish an app on your own domain later, turn on Public HTTP / HTTPS.
  6. Choose Review plan, then check the price and who gets access.
  7. Choose Create VM.

Check it worked: Recent operations shows the creation as Completed, and the VM is under Machines.

Not an administrator? Review plan leaves the plan at the top of Compute for 24 hours, for an administrator to create.

VMs and environments explains providers, sizes and prices.

Approve a VM plan

Before you start: in the dashboard, you need to be an administrator. With oo, Manage machines (hosts.manage) and Start jobs (jobs.create) are enough, except to create a VM a connected agent asked for; an administrator can give you Manage machines and Start jobs.

  1. Open Compute. Waiting plans show at the top.
  2. Choose Review plan to see who asked, the price and who gets access.
  3. Choose Create VM.
  4. Or, for a connected agent's request, choose Decline. Dismiss hides any other plan.

Check it worked: the plan's card says the VM is being created, then that it is ready.

A plan expires 24 hours after it was made. Ask for a new plan then.

VMs and environments explains who may plan and create VMs.

Resize a VM

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs. Only VMs on OpenOrange capacity or Hetzner resize.

  1. Open Compute.
  2. Open the menu at the end of the VM's row, and choose Resize.
  3. Choose a size. Current size marks the one it has.
  4. If a restart box shows, tick it.
  5. Choose Resize to and the size.

Check it worked: the VM's row shows the new size once the resize is done.

Moves to another server means the VM is off while its disk copies. Ask support marks sizes only support sets up.

VMs and environments explains what a resize restarts.

Add a disk to a VM

Before you start: you need to be an administrator, as volumes are paid. An administrator can make you one. Only VMs on OpenOrange capacity take volumes.

  1. Open Compute, open the VM's row menu and choose Open VM page.
  2. On Disks, choose Add disk.
  3. Fill in Name, Size (GB) and Mount path.
  4. Check the monthly price, then choose Add disk.
  5. On a service VM, run the mount command the job shows, as root in Terminal.

For an agent's VM, use the Server tab on the agent's page instead.

Check it worked: the volume shows under Volumes as Ready.

Volumes aren't in backups or pre-update snapshots. A detached volume keeps its files and is charged until you delete it.

VMs and environments explains what volumes cost.

Power a VM off or on

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs.

  1. Open Compute.
  2. Open the menu at the end of the VM's row.
  3. Choose Power off, Power on or Reboot.
  4. To power off, type the VM's name and choose Power off.

Check it worked: the VM's status shows Stopped, or Ready once it is back.

A powered-off VM is still charged at the same rate. An agent doesn't answer while its VM is off.

VMs and environments explains what VMs cost.

Rename a VM

Before you start: you need Manage machines (hosts.manage) on the VM. Not an administrator? Ask one to give you See machines and Manage machines.

  1. Open Compute.
  2. Open the menu at the end of the VM's row, and choose Rename.
  3. Type the new Name and choose Save.

Check it worked: Machines shows the new name.

oo and the API still take the name the VM was made with.

VMs and environments explains the kinds of VMs.

Check a VM's usage

Before you start: you need to be an administrator. On an agent's VM, oo also works with Chat and settings on every agent there, which an administrator gives on each agent's Access tab (Let people use an agent).

  1. Open Compute. A row may show Mostly idle, CPU busy or Memory busy.
  2. Open the VM's row menu and choose Open VM page.
  3. Monitor shows CPU, memory, disk and network, live.
  4. This week shows its CPU and memory at the 95th percentile, and whether a size change is suggested.
  5. Processes lists the top 10 by CPU or memory.

Check it worked: Monitor shows Live.

A VM that is off or busy with an operation has no live stats.

VMs and environments explains sizes and resizing.

Delete a service VM

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs. Remove the VM's domains first.

  1. Open Compute and choose Domains. Remove every route on the VM.
  2. Choose Machines.
  3. Open the menu at the end of the VM's row, and choose Delete VM.
  4. Type the VM's name and choose Submit deletion.

Check it worked: Recent operations shows Deleted, and the VM moves to Retired.

The VM's data is deleted, and no backup is taken. An agent's VM goes when you delete the agent.

VMs and environments explains what VMs cost.

Open a VM terminal

Before you start: you need to be an administrator with Manage machines (hosts.manage). On an agent's VM, oo also works with Chat and settings on every agent there, which an administrator gives on each agent's Access tab (Let people use an agent).

  1. Open Compute, open the VM's row menu and choose Open VM page.
  2. On Terminal, choose Open terminal.
  3. Confirm with Open terminal.

For an agent's VM, use the Server tab on the agent's page instead.

Check it worked: the terminal shows Connected, and you work as root.

The VM's log names you, and your Sunport records when the terminal opens and closes. If it asks for Sunport access, choose Set up on the Access tab, run the command it shows, then choose Check.

VMs and environments explains who may work on a VM.

Transfer files to a VM

Before you start: you need to be an administrator. On an agent's VM, oo also works with Chat and settings on every agent there, which an administrator gives on each agent's Access tab (Let people use an agent).

  1. Open Compute, open the VM's row menu and choose Open VM page.
  2. On Files, choose Show files.
  3. Open a folder, or type its path and choose Open.
  4. Choose a file or folder's download button, or Upload files.

For an agent's VM, use the Server tab on the agent's page instead.

Check it worked: the uploaded file shows in the folder, or the download is on your computer.

On a service VM, copies run as root. On an agent's VM, they run as the agent's user, so files you upload become the agent's.

VMs and environments explains who may work on a VM.

Reach a VM over SSH

Before you start: you need to be an administrator with Manage machines (hosts.manage). On an agent's VM, Chat and settings on every agent there is enough, which an administrator gives on each agent's Access tab (Let people use an agent).

oo sets this up; the dashboard has no such step.

  1. Print the SSH settings for the VM:

    oo vm ssh-config web-1
    oo vm ssh-config support-bot --agent
  2. Add what it prints to ~/.ssh/config.

  3. Connect to the host named after the VM, for example ssh web-1.

Check it worked: ssh web-1 opens a shell on the VM.

On an agent's VM, you sign in as the agent's user. --root signs in as root, as the host NAME-root.

VMs and environments explains who may work on a VM.

Give an agent VM access

Before you start: you need to be an administrator. An administrator can make you one. The agent asks first.

  1. Open Compute, open the VM's row menu and choose Open VM page.
  2. On Access, find the agent under Access requests.
  3. Read its level and reason, then choose Approve.
  4. Confirm with Approve. Or choose Deny, then Deny request.

For an agent's VM, use VM access on the Server tab of that agent's page.

Check it worked: the agent shows under Who can run commands here, with its access and when it expires.

To end it early, choose Revoke, then Revoke access.

An agent's owner also decides what it asks for on its own VM, by asking Clem.

VMs and environments explains read and root access.

Publish an app

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs. The app listens on one port of a service VM or an agent's VM.

  1. Open Compute and choose Domains.
  2. Choose Add domain.
  3. Under VM, choose the VM the app runs on.
  4. Under Connection, if it shows, choose Through Sunport.
  5. In Hostname, type one name, such as shop. Your Sunport's domain follows it.
  6. In Application port, type the app's port, such as 8080.
  7. Keep Ask for OpenOrange sign-in on, unless the app must be public.
  8. Choose Apply route.

Check it worked: the domain shows DNS ready, and its address opens the app.

Port 22 can't be published.

VMs and environments explains the ways a domain connects.

Publish on your own domain

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs. You need a ready edge gateway, a VM with Public HTTP / HTTPS on, and access to the domain's DNS. In the dashboard, a service VM your Sunport reaches takes only Through Sunport.

  1. Open Compute and choose Domains.
  2. Choose Add domain, and under VM choose the VM.
  3. Under Connection, if it shows, choose Through edge gateway.
  4. In Hostname, type the full name, such as shop.example.com.
  5. Under Edge gateway, choose a gateway, then choose Apply route.
  6. Open the domain's menu and choose DNS & details.
  7. In your DNS, create the CNAME it shows.
  8. Once the domain shows Edge verified, create the A record it shows.

Check it worked: the domain shows Edge verified, and the name opens your app.

The app serves HTTPS on port 443 with its own certificate and keeps its own login. To move a route, choose Move gateway, then Confirm DNS cutover once the new gateway serves it.

VMs and environments explains the ways a domain connects.

Control access to an app

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs. This works for domains Through Sunport only.

  1. Open Compute and choose Domains.
  2. Open the domain's menu.
  3. Choose Turn on sign-in or Turn off sign-in.
  4. To turn it off, confirm with Turn off.

Check it worked: the domain shows OpenOrange sign-in, or says anyone with the address reaches it.

With sign-in on, administrators get through, and on an agent's VM, the people who may use the agent. The app's own login stays behind it. Turning it on takes up to a minute.

VMs and environments explains the ways a domain connects.

Remove a domain

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs.

  1. Open Compute and choose Domains.
  2. Open the domain's menu and choose Remove route.
  3. Type the route's name and choose Remove route.

Check it worked: the domain leaves the list.

A domain may show Removal pending. Once its DNS has changed, choose Finish removal in its menu. The name stays reserved until then.

VMs and environments explains the ways a domain connects.

Add an edge gateway

Before you start: you need to be an administrator with Manage machines (hosts.manage) and Start jobs (jobs.create). An administrator can make you one. The gateway is charged every month until you remove it.

  1. Open Compute and choose New VM.
  2. Under Role, choose Edge gateway.
  3. Fill in Name and ID.
  4. Choose a Provider, a Location / capacity node and a Capacity.
  5. Choose Review and check the monthly price.
  6. Choose Create edge gateway.

Check it worked: the gateway shows under Machines, as Setting up until it is ready.

To remove one, move the web, model calls and routes off it first. Then choose Remove in its menu. Its server is destroyed and its charges stop.

VMs and environments explains edge gateways and what they cost.

Forward a domain

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See machines, Manage machines and Start jobs. You need a ready edge gateway of your own, and a server that serves HTTPS.

  1. Open Compute and choose Domains.
  2. Under Routes to servers, choose Forward a domain.
  3. Fill in Hostname, Route name and Edge gateway.
  4. Fill in the Server address and Port.
  5. If the server's certificate is for its address, type that in Certificate name.
  6. Optionally, limit Paths, or turn on Refuse other sites' pages or No cookies.
  7. Choose Apply route.

Check it worked: the route shows under Routes to servers, and the name opens the server.

Its DNS works as for your own domain: the CNAME first, then the A record. oo vm domains list names both. oo vm domains unforward vnc stops forwarding.

VMs and environments explains the ways a domain connects.

Route traffic through a gateway

Before you start: you need Manage machines (hosts.manage) and Start jobs (jobs.create), and a ready edge gateway. Not an administrator? Ask one to give you See machines, Manage machines and Start jobs.

  1. Open Compute and choose Domains.
  2. Under Sunport traffic, choose a gateway for Web and for Model calls.
  3. Choose Save.
  4. For a backup, turn on Failover, pick Backup 1, and choose Turn on failover. It needs a second ready gateway.

Check it worked: Web and Model calls show the gateways you saved. With failover on, Serving now names the gateway in use.

While failover is on, the route can't change. Turn it off and wait about ten minutes first.

VMs and environments explains edge gateways and what they cost.

Create an environment

Before you start: you need Request environments (environments.create), and a profile to create from. Not an administrator? Ask one to give you See environments and Request environments.

  1. Open Compute and choose Environments.
  2. Choose Create machine.
  3. Choose a Profile, and how long it Runs for.
  4. Under Lifetime, keep On-demand, or choose Keep running until deadline.
  5. Add a Purpose (optional).
  6. If Delete its data on shows, choose the day.
  7. Choose Create machine.

Check it worked: it says Machine created, and the list shows it Running.

Some profiles offer One from the pool. It runs until its deadline; choose Give back when you're done.

VMs and environments explains lifetimes and what environments cost.

Run commands in an environment

Before you start: you need Run commands and open environments (environments.use), on your own environment. Not an administrator? Ask one to give you See environments and Run commands and open environments. It must be running.

  1. Open Compute, choose Environments and open the environment.
  2. On Runs, type the Command, such as make test.
  3. Optionally, set a Working folder and Files to keep.
  4. Choose Run.

Check it worked: the run shows Succeeded and its exit code, with its Output.

Your Sunport keeps a run's output and kept files for a limited time. A run never starts a stopped environment.

VMs and environments explains environments.

Transfer files to an environment

Before you start: you need Run commands and open environments (environments.use), on your own environment. Not an administrator? Ask one to give you See environments and Run commands and open environments. It must be running.

  1. Open Compute, choose Environments and open the environment.
  2. On Files, type a folder's path and choose Open.
  3. Choose a file to read or edit it, then Save. Or choose Download.
  4. To add one, choose Upload a file. It takes up to 8 MB.

Check it worked: the file shows in the folder.

Files work only while the environment runs. Reading them never starts it.

VMs and environments explains environments.

Open an environment terminal

Before you start: you need Run commands and open environments (environments.use), on your own environment. Not an administrator? Ask one to give you See environments and Run commands and open environments. It must be running.

  1. Open Compute, choose Environments and open the environment.
  2. Choose Terminal.

Check it worked: the terminal shows Connected.

A terminal, an SSH session or a forwarded port keeps an on-demand environment from stopping idle.

VMs and environments explains lifetimes.

Preview an app

Before you start: you need Run commands and open environments (environments.use), on your own environment. Not an administrator? Ask one to give you See environments and Run commands and open environments. It must be running.

  1. Open Compute, choose Environments and open the environment.
  2. On Ports, type the Port and choose Open port.
  3. Choose Open preview. It opens in a new tab.

Check it worked: the new tab shows your app.

To stop it, choose Close, then Close port.

Some Sunports serve no previews yet. Ports then says so.

VMs and environments explains environments.

Control a macOS environment

Before you start: you need Run commands and open environments (environments.use), on your own macOS environment. Not an administrator? Ask one to give you See environments and Run commands and open environments. It must be running.

  1. Open Compute, choose Environments and open the environment.
  2. Choose Desktop. The screen shows live.
  3. Click on it, or press Command shortcuts.

Check it worked: the screen changes as you click.

Typed characters don't arrive yet. Put text in place with a run or a file copy instead.

VMs and environments explains environments.

Stop, extend or delete an environment

Before you start: it must be your environment, or you need Manage everyone's environments and connections (environments.manage). Stopping and deleting need Stop and delete environments (environments.delete). Extending needs Request environments (environments.create). An administrator can give you each.

  1. Open Compute, choose Environments and open the environment.
  2. Choose what you need:
    • Extend: pick a New deadline, then choose Extend.
    • Stop: confirm with Stop. It keeps its data; Start runs it again before its deadline.
    • Delete: confirm with Delete. The machine and its data are gone.

Check it worked: the environment shows its new deadline, Stopped, or Deleted.

An environment that keeps no data has no Stop: delete it when you're done.

VMs and environments explains lifetimes and kept data.

Restore an environment

Before you start: this works only on your own Namespace workspace. Restoring needs Run commands and open environments (environments.use) on your environment, and it must be stopped. Cloning needs Request environments (environments.create). An administrator can give you either.

  1. Open Compute, choose Environments and open the environment.
  2. Under Snapshots, find the restore point.
  3. Choose Restore and confirm with Restore.
  4. Or choose Clone, then Create machine, for a new machine from it.

Check it worked: the machine starts from the snapshot, or Machine created shows with Open it.

A restore loses what changed on the machine since the snapshot.

VMs and environments explains environments.

Set environment spending caps

Before you start: you need to be an administrator. An administrator can make you one.

  1. Open Compute and choose Environments.
  2. Under Spending caps, choose Set caps.
  3. Choose the Member or agent.
  4. Fill in Maximum machines at once, Maximum spend (USD) or both.
  5. With a spending cap, set the Window (days), from 1 to 30.
  6. Choose Set caps.

Check it worked: the caps show under Spending caps, with current use.

To lift them, choose Remove caps.

Caps never grant permission. Removing caps doesn't stop machines that run.

VMs and environments explains what environments cost.

Add an environment profile

Before you start: you need Manage everyone's environments and connections (environments.manage). Not an administrator? Ask one to give you See environments and Manage everyone's environments and connections.

  1. Open Compute and choose Environments.
  2. Under Profiles, choose New profile.
  3. Choose the Machine, and fill in Name.
  4. Under When its time is over, choose what happens to its data.
  5. Set Longest it runs.
  6. Choose Create profile.

Check it worked: the profile shows under Profiles.

Revise and Archive change only new machines. Machines already made keep their revision.

VMs and environments explains profiles.