JDoodle Compiler API
Credit-metered compile-and-run REST and WebSocket API from the JDoodle online IDE, covering 114 languages, frameworks and databases, with each run costing one credit and a free daily allowance. A convenient credit-metered compiler API for demos and courses; limits and isolation are too thinly documented for untrusted agent workloads at scale.
Overview
JDoodle Labs Pty Ltd (Australia) runs the JDoodle online IDE and sells its Compiler API separately. POST https://api.jdoodle.com/v1/execute returns output, status code, memory and CPU time in one response, and a WebSocket connection streams output as it is produced and lets the user answer prompts. The API covers 114 languages, frameworks and databases with multiple selectable versions. The product page describes a fresh sandbox per run with its own filesystem and process limits, which can kill non-terminating programs and has no route to your network; the technology is not named.
Billing is a daily-resetting credit model: one run is one credit, and a WebSocket session, a multi-file upload or Internet access each add one more. The free API plan grants credits every day; paid tiers are a separate monthly or yearly subscription from the platform plans (Free, Student $4, Pro $12, Teacher $20 per month). Execution time and memory limits are not published. There is no SDK, self-hosting or compliance documentation, and no state persists between calls.
Notable
- Credits reset daily; one run equals one credit, with WebSocket, multi-file and Internet access each costing one extra credit
- 114 languages, frameworks and databases, each with several versions
- Platform plans from US$0 (1,000 code executions per day) to Teacher US$20/month; the API is billed separately
JDoodle Compiler API specifications
| Attribute | Details |
|---|---|
| Isolation | Vendor does not name the technology; the product page says each run gets "a fresh sandbox with its own filesystem and process limits" that can stop a never-ending program and has no route to your network |
| Deployment | Hosted platform |
| Open source | No |
| SDKs and interfaces | REST API |
| Cold start (vendor claim) | Not documented |
| Max session length | Not documented |
| Persistence | None; each REST call is one run. A WebSocket mode streams output and accepts input while a program runs, and multi-file projects can be uploaded for one credit extra |
| GPU | No GPU option is documented |
| Networking | No Internet access by default; giving code Internet access costs one extra credit per run |
| Pricing | One credit per run; opening a WebSocket connection, uploading a multi-file project and enabling Internet access each add one credit; credits reset daily. Paid API tiers are a separate subscription from the platform plans and are listed on the pricing page (figures only rendered in-browser, not retrievable here) |
| Free tier | Free API plan with a daily credit allowance (the docs say it is enough to work through the documentation; the amount is not stated on the docs page) |
| Compliance | Not documented |
| Regions | Not documented |
Facts from JDoodle Compiler API’s public documentation, verified November 9, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- You want a simple per-run API with a free daily allowance for prototyping
- You need interactive programs: the WebSocket mode streams output and accepts input mid-run
- You are embedding execution in an education product alongside the embeddable IDE
Trade-offs
- Execution time, memory and output limits are not documented
- Sandbox technology is not named; isolation is described only as a fresh filesystem and process limits
- Stateless, with Internet access and multi-file projects costing extra credits per run
- Paid API tier prices are only rendered in the browser; no SDKs or compliance information
Good fit for: Low-volume, pay-per-run execution with an interactive stdin stream for teaching and demo products.
How JDoodle Compiler API compares
| Sandbox | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|
| JDoodle Compiler API | Fresh sandbox per run (unnamed) | No | No / No | Not documented | Not documented | No / No | No | REST API |
| OneCompiler Code Execution API | Not documented | No | No / No | Not documented | 7-20 s (enterprise) | No / No | No | REST API |
| Judge0 | isolate (namespaces/cgroups) | Yes | Yes / No | Not documented | 5 s wall (max 20 s) | No / No | No | REST API, Python, JavaScript/TypeScript |
| Sphere Engine | Isolated workspace (unnamed) | No | Yes / No | Not documented | 5 s (1-15 s) | No / Not documented | No | REST API, PHP, Python, JavaScript/TypeScript |
| Piston | isolate in Docker | Yes | Yes / No | Not documented | 3 s run / 10 s compile | No / No | No | REST API |
| Codapi | Locked-down Docker container | Yes | Yes / No | 1-3 s per run (claim) | 5 s default | No / No | No | REST API, JavaScript/TypeScript |
Frequently asked questions
What is JDoodle Compiler API?
How does JDoodle Compiler API isolate code?
Is JDoodle Compiler API open source?
How much does JDoodle Compiler API cost?
What are the alternatives to JDoodle Compiler API?
Sources
Cite this page
Agent Sandboxes. (2026). JDoodle Compiler API. agentsandboxes.org. Last reviewed November 9, 2026. https://agentsandboxes.org/sandboxes/jdoodle/
Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.