Vol. 1 · No. 331Blender 3.6 / 4.2 / 4.5 / 5.0 / 5.2 / 5.3Cycles · EEVEE
JANCTION
Render · Blender on RTX PRO 6000 · Tokyo
0.1 JPYper GPU-secondFirst 100 JPYfree, no card
Front page / Keep your Blender renders and scenes

Keep your Blender renders and scenes

Subscribe to a JANCTION Render monthly plan. Every plan includes JANCTION Storage (beta) (Basic 200 GiB, Standard 1 TiB for 3 people, Pro 5 TiB for 5 people): each finished render and its source scene are saved automatically and kept with no expiry for as long as you are subscribed. The final's reply carries a one-time link to open it, and your AI or the browser workbench can render any saved version again with the same settings. Every plan uploads .blend files up to 10 GB. Without a plan, files are deleted 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total). AI agents connect at https://render.janction.jp/mcp (remote MCP with OAuth; connecting creates a free key).

Updated 2026-11-17

What it does Your own .blend, bpy script or 3D file (glTF/GLB, FBX, USD, OBJ...) rendered to images or video on a cloud NVIDIA GPU, from an AI app, the terminal or the browser. The first preview needs no payment.
What it does not do It does not speed up the Blender viewport on your machine, does not take non-Blender video, simulations or general GPU jobs, and an AI that is not connected cannot render on its own.

Try your own file for freeBuild it with an AI and try

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.

What each plan includes

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, Pro 5 TiB for 5). .blend uploads go up to 10 GB.

Monthly planJANCTION Storage (beta)People.blend uploads
Basic (1,500 JPY a month)Personal: 200 GiB1up to 10 GB
Standard (4,500 JPY a month)Pro: 1 TiB3up to 10 GB
Pro (15,000 JPY a month)Team: 5 TiB5up to 10 GB

How it works

  1. Render as usual from your AI (MCP), the browser workbench or the command line.
  2. When a render finishes, it goes into JANCTION Storage (beta) with its source scene. Nothing to save by hand.
  3. The final's reply carries a one-time link that opens it in storage; the browser workbench opens it too. Each version lists its results and source scene.
  4. To continue, ask your AI: "Open my last render and render it again with warmer light." It starts from the saved scene with the same settings.

What to say to the AI

Open the render I made last week and render it again at 4K with the same camera.

Show me the versions of this scene I have kept.

After cancelling

Your plan runs to the end of the paid month. After that, saved work gets an expiry and can still be opened and downloaded for 90 days; you are told before the expiry. What is left of the plan's monthly credit ends with the paid month; credit you topped up stays.

Without a monthly plan

Files are deleted 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total). Download what you need, or subscribe to keep it. How other render farms compare: how long render farms keep your renders.

Connect

fromhow
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 / EnterpriseAn 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)
ChatGPTPlugins (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 Codeclaude 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)
Codexcodex 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 CodeAdd 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 CLIagy 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
OpenCodeAdd https://render.janction.jp/mcp under mcp in ~/.config/opencode/opencode.json with "type": "remote", then opencode mcp auth janction-render (OAuth). Guide
Qwen Codeqwen 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 CLIcopilot 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 ChatAdd 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
ManusConnectors → 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 CLIKiro: "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 StudioTools → 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 StudioSettings → 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 clientsStreamable 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

FAQ

Which plan should I pick?

Basic if you work alone (200 GiB). Standard if up to 3 people share the work (1 TiB). Pro for a team of up to 5 (5 TiB). Every plan uploads .blend files up to 10 GB.

Do I have to save renders by hand?

No. Every finished render and its source scene are saved automatically while you are subscribed.

Is JANCTION Storage a separate sign-up?

No. It comes with the JANCTION Render monthly plan; the link in a final's reply opens it.

What happens to my work if I cancel?

After the paid period ends, saved work can be opened and downloaded for 90 days, and you are told before the expiry.

Related

Overview · All guides · llms.txt