How it works
Four steps, nothing to pay while idle
Set the image and command
Paste an image reference and the command to run, just like in XPod Run. Then pick a size: J512, J1024 or J2048.
Pick a schedule
Use a cron schedule for recurring tasks (the default time zone is Asia/Jakarta), or run it right now with one click.
Runs isolated
The container starts when its time comes, runs apart from other customers, and stops when it finishes.
Pay per second it runs
What is billed is the seconds the container runs until it finishes. While the job is idle, nothing is charged.
Seven products, one platform
Which one do you need?
The difference is when your code runs: from always on, to not running at all until it is needed.
- What you bring
- An app from the catalog
- When it runs
- Always
- How it is billed
- Monthly
- What you bring
- Your own container image
- When it runs
- Always
- How it is billed
- Monthly, per active minute
- What you bring
- A PostgreSQL database
- When it runs
- Always
- How it is billed
- Monthly
- What you bring
- Static files
- When it runs
- Never
- How it is billed
- Plan + bandwidth
- XPod Jobsyou are here
- What you bring
- Code in a container
- When it runs
- On a schedule
- How it is billed
- Per second of execution
- What you bring
- Code or a container
- When it runs
- When messages arrive
- How it is billed
- Per processed message
- What you bring
- One function (handler)
- When it runs
- When called
- How it is billed
- Per call + GB-second
Good for
Tasks that don't need a server running 24 hours
Daily database backup
Dump the database every night, upload it to storage, then finish.
0 3 * * *
Weekly report
Put together a sales summary every Monday morning and send it to the team by email or WhatsApp.
0 7 * * 1
Pull data from a partner API
Fetch the latest data from a partner system every hour and store it in your database.
0 * * * *
How billing works
Seconds running, not hours waiting
Three sizes
J512 (0.5 vCPU / 512 MB), J1024 (1 vCPU / 1 GB) and J2048 (2 vCPU / 2 GB). About Rp1.30, Rp2.59 and Rp5.19 per minute.
Per second, not per hour
What is billed is the seconds the container runs. While there is no execution, there is no charge.
Taken from your balance
No card is charged automatically. Charges are taken from your XPod balance; you need at least Rp10,000 to start.
See the pricing details →
Good to know
A few ground rules
- A time limit is required
- Every job must set a time limit for its executions. A process with no limit is not accepted, so your bill can't balloon without you noticing.
- You set the retries
- You decide how many times a failed execution may be attempted.
- Schedules are read in WIB
- Unless you name another time zone, cron schedules are read in Asia/Jakarta (WIB).
- Run it any time
- No need to wait for the schedule: one click runs the job outside it, and you can see the history of every execution in the console.
When not to use XPod Jobs
Jobs is not for everything, and that's fine
It has to stay running
A process that must always be ready for connections fits Run better, at a fixed monthly price.
Go to XPod Run →Processing messages that arrive at random
If work shows up outside a schedule, a queue starts its processor only when there is a message.
Go to XPod Queue →Answering HTTP requests
For code that is called per request and must answer straight away, use Functions.
Go to XPod Functions →