Updated 2026-10-01
JANCTION Render runs Blender, not Arnold, Redshift, Karma or Cinema 4D's renderers, so the tools for Maya, Houdini and Cinema 4D do one thing: export the scene to a file Blender imports (USD or FBX from Maya, Alembic or USD from Houdini, FBX or USD from Cinema 4D), upload it with the textures it references, render it with Cycles on an NVIDIA RTX PRO 6000 and open the result. Geometry, animation, cameras and basic textured materials carry over; renderer-specific shaders, render passes and most lights do not, so the scene is lit with the studio HDRI preset by default. Preview (4 frames), Final (MP4) and Turntable buttons; free beta, 10 GPU-minutes per key per day.
| application | export | install | what you get |
|---|---|---|---|
| Maya 2022+ | USD (mayaUsdPlugin, materials as UsdPreviewSurface) or FBX (baked animation) | copy jr_submit.py and janction_render_maya.py into Documents/maya/scripts; run import janction_render_maya; janction_render_maya.show() in the Script Editor (drag it to a shelf for a button) | a window with export format, frame range, lighting preset, final size and samples; Preview / Final (MP4) / Turntable |
| Houdini 18.5+ | Alembic of /obj (geometry and cameras), an existing USD ROP, or a file on disk | a shelf tool whose Python calls janction_render_houdini.main() | one dialog for the numbers and the mode; progress in the status bar |
| Cinema 4D R23+ | FBX (cameras, lights, tracks and materials on) or USD when the exporter is installed | Script → Script Manager → Import Script; keep jr_submit.py next to it | a small dialog with the same fields and buttons; Cancel stops the job |
Code and the full install notes: integrations/ on GitHub. The tools use only the Python inside each application (standard library, nothing to pip-install) and keep the application responsive: upload, wait and download run in a background thread. The first run creates a free key and stores it in ~/.janction_render.json.
studio HDRI preset lights the scene by default (sunset / overcast / night, or "scene lights only" to turn it off).sheet.png, a few GPU seconds. Look, adjust the export or the lighting, send again (identical files are not uploaded twice).Results open in the OS viewer and are saved under ~/janction_render/<application>/. Measured times for comparable jobs are on the benchmarks page.
Export USD, FBX, glTF, OBJ, Alembic, STL or PLY and use the command line: pip install janction-render, then janction-render render model.usd --environment studio --orbit. AI agents do the same through the MCP server (https://render.janction.jp/mcp) with scene_url or a local path.
Free beta (as of 2026-10-01): 10 GPU-minutes per key per day (20 per network), final renders up to 240 frames at 1080p. No sign-up: connecting creates a key. Inputs and results are deleted 24 hours after last use and never used for training. Paid plans will be announced on this site and in llms.txt before they start.
No. The farm runs Blender with Cycles. The export carries geometry, animation, cameras and basic textured materials; renderer-specific shaders are dropped. Use it for previews, turntables and animations where a Cycles look is fine.
No. Blender runs on the JANCTION worker. You need only the export plug-in of your application (USD, FBX or Alembic).
Lights rarely survive FBX, USD and Alembic exports, so the tools light the scene with the studio HDRI preset. Pick sunset, overcast or night, or turn the preset off to use whatever lights the import produced.
They are uploaded next to the exported file under their file names and deleted with everything else 24 hours after last use. Files render in a container with no network access (security).
JANCTION Render v0.4.5 · JasmyLab Inc. · 日本語