FAQ

Who bills me for the compute?

Your providers, in your own accounts. Portal's figures are estimates from recorded rates and running times. See Prices and quotes.

Which providers can I use?

AWS, Google Cloud, Azure (VMs and Container Apps), Modal, Lambda, and machines you enroll. See Providers.

Does a job continue on its own after a spot notice?

No. Portal checkpoints and suspends it, and waits. You resume it on a machine you choose, and it continues from where it paused. See Spot interruptions and checkpoints.

Does Portal move my jobs without asking?

Yes, to a cheaper offer when it saves at least 20% and 3 times the move's cost, and back to spot on the same terms. Turn either off per job or in Settings. A job launched with an exact --on is never moved that way. See What Portal does on its own.

Can a coding agent spend money without me?

An agent can run jobs with the access its sign-in holds. Limit it with a connection cap, a job budget, or an agent token with a budget. It cannot change settings or connect a cloud through --from-cli without your agreement. See Spend caps and budgets and Agent context.

Do I need a coding tool?

No. The CLI and the console do everything a coding tool does. See Quickstart.

Which Python versions?

3.12 by default, 3.13 or 3.14 through .python-version. See Run a job.

Does it run on Windows?

The CLI runs on macOS and Linux. On Windows, use WSL.

How long are my outputs kept?

7 days after the job ends; logs 30 days. See Checkpoints and retention.

What happens to my own machine when a job ends?

Nothing beyond the job: Portal never powers it off or reboots it. See Your own machines.

Can I delete old jobs?

Yes, ended ones: portal rm JOB, or portal rm --ended --project NAME. They leave every listing; costs still count them. See Move, suspend and resume.

What can a checkpoint not carry?

Open files, sockets, threads, other processes, and files outside the working directory. See what a checkpoint cannot carry.