Updated 2026-10-07
Yes, a company can use JANCTION Render today: it is a free beta operated by JasmyLab Inc. (Tokyo), provided as is without an availability guarantee, with no sign-up (a key per person or per pipeline), spend caps per key, and inputs and results deleted 24 hours after last use and never used for training. There are no invoices yet; monthly plans with commercial-use terms, several keys and email support are planned (Starter 2,980 JPY for 15 GPU-hours, Pro 14,800 JPY for 90, Scale 59,800 JPY for 360, as of 2026-10-07) and will be announced before any charge. An independent security test of the public API, the MCP endpoint and the OAuth flow was run in October 2026 and its findings fixed; a second isolation layer in the datacenter is still open before paid keys are issued. There is no sales team: the service is self-serve, and questions go to the support page.
| Question | Answer (free beta, 2026-10-07) |
|---|---|
| Who operates it | JasmyLab Inc., Tokyo (legal notice) |
| Terms | terms: beta provided as is, no availability guarantee, no SLA; you own your renders |
| Where the data goes | scenes and renders are stored on the service's servers in Japan for the job and deleted 24 hours after last use; share pages keep a copy only if you create one; privacy |
| Training | inputs and results are never used to train models |
| Accounts | none: a key per person or pipeline (POST /v1/keys or the OAuth consent page); keys can be revoked; spend and daily caps per key (POST /v1/me/limits) |
| Security | independent black-box test of the API, MCP and OAuth in October 2026, findings fixed; renders run in throw-away containers with a read-only root; a second isolation layer in the datacenter is still open before paid keys; security |
| Invoices | not yet; the beta is free. Invoices and receipts come with the paid plans |
| Support | support page; email support with a next-business-day target is part of the planned Pro plan |
| Status | status, /v1/health, changelog |
| Plan | Price per month | Included GPU time | For |
|---|---|---|---|
| Free beta | 0 | 10 GPU-minutes per key per day; 240 frames at 1080p per job | trying it, agents' previews, small renders |
| Starter | 2,980 JPY | 15 GPU-hours | one person or one pipeline; commercial use; webhooks; 3 keys |
| Pro | 14,800 JPY | 90 GPU-hours | a team; queue priority; 10 keys; email support |
| Scale | 59,800 JPY | 360 GPU-hours | products that render for their own users |
Metered use is planned at 0.1 JPY per GPU-second. Details and the current state are on pricing and products; the numbers above are the plan as of 2026-10-07 and may change before launch.
POST https://render.janction.jp/v1/keys or the OAuth consent page of the MCP client. Keep keys in a secret store.POST /v1/me/limits with a per-job and per-day budget, so an agent cannot overspend once metering starts.notify_url instead of polling and Idempotency-Key on job submissions so retries do not double-render.https://render.janction.jp/mcp; the tool descriptions tell them when to use the service and when a local render is faster.What this is not: a managed studio pipeline, a many-node farm for long sequences, or a service with a sales team and custom contracts (see the large farms for that). It is a render tool for agents and scripts that a team can adopt in an afternoon.
| 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) | Settings → Connectors → Add custom connector → https://render.janction.jp/mcp. "Connect" opens a page that creates a free key |
| ChatGPT | Settings → Connectors → Advanced → Developer mode → Create → https://render.janction.jp/mcp (OAuth) |
| Claude Code | claude mcp add --transport http janction-render https://render.janction.jp/mcp, then /mcp to authenticate |
| Codex | codex mcp add janction-render --url https://render.janction.jp/mcp |
| Cursor / VS Code | Add to Cursor Add to VS Code The button opens the editor; confirm and it is added. Manual: Streamable HTTP at https://render.janction.jp/mcp |
| Gemini CLI / Antigravity CLI | gemini extensions install https://github.com/JasmyLab-JANCTION/janction-render |
| Grok / Perplexity / Le Chat | Add a custom (remote MCP) connector with https://render.janction.jp/mcp in each app's Connectors settings (Grok: New Connector → Custom; Perplexity: Pro / Max / Enterprise; Le Chat: workspace admin) |
| Windsurf, Cline, Goose, other MCP clients | Streamable HTTP at https://render.janction.jp/mcp; OAuth or Authorization: Bearer <api key> |
| 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 |
Not during the free beta, because nothing is charged. Invoices and receipts come with the paid plans; the plan and its launch will be announced on the changelog before any charge.
Better not: a key is the unit of quota, caps and revocation. Make one per person or per pipeline; the planned plans include 3 to 10 keys.
In a datacenter in Japan operated for JasmyLab. Scenes and renders stay there for the job and are deleted 24 hours after last use.
No. The beta is provided as is; the GPU may be lent to another workload for a while, and jobs queue until it returns (the tools report the expected wait). An SLA is not part of the planned plans either.
Use the support page. There is no sales team; questions about the planned plans are answered there too.
JANCTION Render v0.4.20 · JasmyLab Inc. · Updated 2026-10-07 · Tested with Blender 5.0, JANCTION Render 0.4.20 · 日本語