RebusFarm, GarageFarm.NET and Fox Renderfarm are commercial render farms for studios: you submit from a desktop client or plugin, they spread a job over tens or hundreds of nodes, and you pay per node-hour, GHz-hour or OctaneBench-hour with volume discounts and $25 trial credits. JANCTION Render is a render service for AI agents: Claude, ChatGPT, Codex or Cursor call it as an MCP tool or an HTTP API, send a .blend, a bpy script or a 3D file, see a tiled preview in seconds, and get frames or an MP4 from datacenter GPUs, with a welcome credit of up to 500 JPY for a new key (100 JPY with no card, 400 JPY more after saving a card that is not charged), then 0.1 JPY per GPU-second (previews free up to 2 GPU-minutes a day; up to 3,000 frames per instruction in automatic internal parts, 1080p on free time and 4K on prepaid credit). For a feature-length sequence on hundreds of nodes with studio support, use the big farms; for a scene an agent wrote ten seconds ago, a product turntable, or a script with no Blender installed, use JANCTION Render. AI agents connect at https://render.janction.jp/mcp (remote MCP with OAuth; connecting creates a free key).
Browser only; no connector or CLI needed. A 100 JPY welcome credit for a new key (14 days, no card; one per network every 30 days, further keys on the same network share what is left), and 400 JPY more for saving a card that is not charged (once per card); after that, previews stay free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second.
| JANCTION Render | GarageFarm.NET | Fox Renderfarm | RebusFarm |
| Who presses the button | an AI agent (MCP tool), a script (HTTP API), you (CLI, Blender add-on) | you, from renderBeamer (desktop client) and DCC plugins | you, online submission or desktop client | you, from their desktop app and plugins |
| Inputs | .blend, bpy script, glTF / FBX / USD / OBJ / STL / PLY / Alembic | Blender and other DCC projects, packaged by the client | Blender and many other renderers' projects | Blender and other DCCs (see their software list) |
| Hardware | NVIDIA RTX PRO 6000 (96 GB); how many are available right now is below the table; frames split into chunks | up to 15 / 30 / 60 GPU nodes or 100 / 150 / 300 CPU nodes per priority tier | CPU and GPU node pools | CPU and GPU pools |
| Price unit | GPU-second (0.1 JPY), after a welcome credit of up to 500 JPY for a new key (100 JPY with no card, 400 JPY more after saving a card that is not charged) (previews free up to 2 GPU-minutes a day); monthly plans from 1,500 JPY a month include JANCTION Storage (beta) | GPU: $0.004 / $0.006 / $0.012 per OctaneBench-hour; CPU: $0.024 / $0.036 / $0.072 per GHz-hour (low / medium / high priority) | CPU: $1.224 per node-hour, down to $0.734 with recharge tiers; GPU rates on their site | see their site |
| Free tier | a welcome credit of up to 500 JPY for a new key (100 JPY with no card, 400 JPY more after saving a card that is not charged), valid 14 days, then previews free up to 2 GPU-minutes a day; no sign-up | $25 trial credits (10 nodes, 30 jobs) | $25 free trial | see their site |
| Results kept (checked 2026-11-16) | 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total). Monthly plans keep them 30 days here and in JANCTION Storage (beta) with no expiry while subscribed (200 GiB to 5 TiB). | 28 days after the job or project; only the first 7 days are guaranteed | source files 20 days | render results deleted 7 days after they are provided |
| Preview before the final | 1 to 4 frames tiled in one image in a few seconds, returned to the agent | test renders via the client | test renders via the client | see their site |
| Estimate | GPU seconds from measured per-frame times before the job | cost estimator on the site | cost estimator on the site | see their site |
| Agent access | remote MCP (OAuth), stdio MCP, OpenAPI, webhooks | no public agent API found | no public agent API found | no public agent API found |
| Support | support page; provided as is | email; 24/7 on medium and high priority | 24/7 per their site | per their site |
GPUs available right now: 3 (from /v1/health). The number updates itself when GPUs are added.
Units are not comparable (an OctaneBench-hour measures GPU throughput, a GHz-hour CPU throughput, a node-hour a whole machine), so the honest comparison is one of your own scenes on each. Measured on JANCTION Render: a 1080p Cycles still in 6 to 10 GPU-seconds, a 24-frame 720p turntable in 58 GPU-seconds (costs).
They combine: iterate on JANCTION Render, then send a long final sequence to a many-node farm. Other comparisons: BlendSwap, SheepIt, render farm APIs, all.
| from | how |
| A file on this computer (.blend, 3D file) | Drop it at /upload to get a 12-hour link (no sign-up), then tell the AI "Render this file: <link>". From inside Blender use the add-on; from a terminal the CLI uploads directly |
| Claude.ai (web / desktop / mobile) | Plugins (older menu: Customize → Connectors) → Add custom connector → https://render.janction.jp/mcp. "Connect" opens a page that creates a free key |
| Claude Team / Enterprise | An owner adds https://render.janction.jp/mcp under Organization settings → Connectors; each member then presses Connect with their own account. In organizations that turn Skills off, Claude Desktop also blocks plugins from November 30 (use the connector URL, or ask the admin to turn Skills on) |
| ChatGPT | Plugins (left sidebar) → Add → Create plugin → https://render.janction.jp/mcp (OAuth). Attach your .blend to the chat. On Business workspaces an admin adds it and shares it |
| Claude Code | claude mcp add --transport http janction-render https://render.janction.jp/mcp, then /mcp to authenticate |
| Claude Code on the web (claude.ai/code) | The same connector as Claude.ai: Plugins (older menu: Customize → Connectors) → Add custom connector → https://render.janction.jp/mcp. Works without changing the session's network settings (guide) |
| Codex | codex mcp add janction-render --url https://render.janction.jp/mcp (the sign-in page opens right away; if Codex later says the server needs login, run codex mcp login janction-render; with a key, add --bearer-token-env-var JANCTION_RENDER_API_KEY) |
| Cursor / VS Code | Add to Cursor Add to VS Code Add to LM Studio The button opens the editor; confirm and it is added. Manual: Streamable HTTP at https://render.janction.jp/mcp |
| Antigravity CLI / Gemini CLI | agy plugin install https://github.com/JasmyLab-JANCTION/janction-render or gemini extensions install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill) |
| Kimi Code (Kimi K3 and other models) | /plugins install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill), or add https://render.janction.jp/mcp as a url entry under mcpServers in ~/.kimi-code/mcp.json and run /mcp-config login janction-render (OAuth). Guide |
| OpenCode | Add https://render.janction.jp/mcp under mcp in ~/.config/opencode/opencode.json with "type": "remote", then opencode mcp auth janction-render (OAuth). Guide |
| Qwen Code | qwen extensions install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill), or qwen mcp add --transport http janction-render with https://render.janction.jp/mcp (stored as httpUrl). Guide |
| GitHub Copilot CLI | copilot mcp add --transport http janction-render with https://render.janction.jp/mcp, then /mcp auth janction-render in copilot (OAuth). With the skill: copilot plugin marketplace add JasmyLab-JANCTION/janction-render, then copilot plugin install janction-render@janction-render. Guide |
| DeepSeek Harness (dsh) | One @deepseek-ai/dsh-mcp-client entry: transport: streamable-http, url: https://render.janction.jp/mcp, headers Authorization: Bearer with a key from POST /v1/keys (no OAuth). DeepSeek guide (API function calling too) |
| Grok / Perplexity / Le Chat | Add a custom (remote MCP) connector with https://render.janction.jp/mcp in each app's Connectors settings (Grok: Plugins → New connector → Custom, guide; Perplexity: Settings → Connectors → Custom → Remote, Pro / Max / Enterprise, OAuth; Le Chat: workspace admin, OAuth or a Bearer key) |
| Gemini app (gemini.google.com) | On the web: Settings → Connected Apps → Custom apps, add the MCP URL https://render.janction.jp/mcp (web only, English interface, with activity saving on). Sign-in is the OAuth consent page |
| Manus | Connectors → Create → Add MCP by URL with https://render.janction.jp/mcp (remote MCP only; OAuth or a Bearer key) |
| MiniMax (MiniMax Code) | One streamable-http entry in the MCP settings: url https://render.janction.jp/mcp, and Authorization: Bearer jr_… in headers |
| Notion (Notion Agent) | Business / Enterprise: Settings → Connections → Discover → Add Custom MCP → https://render.janction.jp/mcp, then sign in (the button shows when a workspace admin allows custom MCP servers) |
| JetBrains (AI Assistant, Junie) | AI Assistant: Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add → connect over HTTP with {"mcpServers": {"janction-render": {"url": "https://render.janction.jp/mcp"}}}. Junie: the same url in ~/.junie/mcp/mcp.json (Authorize opens the browser), or "headers": {"Authorization": "Bearer jr_…"} |
| Kiro (IDE, CLI) / Amazon Q Developer CLI | Kiro: "url": "https://render.janction.jp/mcp" under mcpServers in ~/.kiro/settings/mcp.json (in the IDE, open a folder: MCP SERVERS appears in the Kiro panel and the authorization page opens; in the CLI, /mcp auth janction-render). With a key: "headers": {"Authorization": "Bearer ${JANCTION_RENDER_API_KEY}"} (add the variable to Mcp Approved Env Vars). Amazon Q Developer CLI: "type": "http" and the same url in the agent configuration, then /mcp to sign in |
| Microsoft Copilot Studio | Tools → Add a tool → New tool → Model Context Protocol → Server URL https://render.janction.jp/mcp. Authentication: OAuth 2.0 with Dynamic discovery, or API key (Header, name X-API-Key, value jr_…). Set the agent's Settings → Generative AI → Orchestration to Yes (generative orchestration), or it will not use the tool |
| LM Studio (0.3.17 or later) | Program tab → Install → Edit mcp.json: {"mcpServers": {"janction-render": {"url": "https://render.janction.jp/mcp", "headers": {"Authorization": "Bearer jr_…"}}}} |
| Cherry Studio | Settings → MCP Servers → Add → Import from JSON: {"mcpServers": {"janction-render": {"type": "streamableHttp", "baseUrl": "https://render.janction.jp/mcp"}}}. Turn it on and press "Sign-in required." to open the consent page in the default browser. If no tools show after signing in, turn the server off and on again (with a key: "headers": {"Authorization": "Bearer jr_…"}) |
| Windsurf, Cline, Goose, Amp, Auggie, Warp, Zed, Roo Code, Continue and other MCP clients | Streamable HTTP at https://render.janction.jp/mcp; OAuth or Authorization: Bearer <api key> |
| Claude Desktop and other stdio-only clients (npm) | npx -y janction-render (in the client's mcpServers: {"command": "npx", "args": ["-y", "janction-render"]}). The npm package janction-render bridges stdio to https://render.janction.jp/mcp with OAuth; --key jr_… for a key you have, --local for the Python stdio server through uv |
| Terminal (stdio, sends local files) | claude mcp add janction-render -e JANCTION_RENDER_SERVER=https://render.janction.jp -- uvx --from janction-render janction-render-mcp |
| Inside Blender (for people) | The add-on; extension repository https://render.janction.jp/extensions/index.json. Maya / Houdini / Cinema 4D: submit tools |
Is JANCTION Render cheaper?
Not comparable by unit. At 0.1 JPY per GPU-second a 24-frame 720p turntable is about 6 JPY and a 1080p still under 1 JPY; the big farms bill per node-hour or benchmark-hour with volume discounts. Run your own scene on each to know.
Can JANCTION Render take a 4K, 2,000-frame sequence?
Yes: up to 3,000 frames per instruction (rendered as automatic internal parts under one job id and joined into one video), and 4K needs prepaid credit. The service runs on a small number of GPUs (the live count is in /v1/health), so a studio-scale job still belongs to a big farm.
Does it support V-Ray, Arnold or Redshift?
No. Blender with Cycles (and EEVEE) only. The large farms support many renderers through their plugins.
Can I keep my renders?
Every monthly plan includes JANCTION Storage (beta): renders and scenes are kept for as long as you are subscribed (Basic 200 GiB, Standard 1 TiB for 3 people, Pro 5 TiB for 5 people). .blend uploads go up to 10 GB. After cancelling, saved work can still be opened and downloaded for 90 days after the paid period ends.
Can I continue from an earlier render?
Yes, on a monthly plan. A final's reply carries a one-time link to open it in storage, where each version lists its results and source scene. Ask your AI to open the earlier render and render it again with the same settings, or open it from the browser workbench.
Can I upload a large .blend file?
Every monthly plan uploads .blend files up to 10 GB. Scenes with packed textures can be sent as they are and rendered to the final.
Why would an agent not use the big farms?
They are driven from a desktop client, so there is no tool an agent can call, no preview it can look at, and no estimate it can quote. JANCTION Render is built as a tool: MCP, HTTP API, previews and estimates in the response.