Forge

Overview

Forge is a single creative workspace that replaces the need for separate design, video, 3D, CAD and automation tools. Graphic design, web design, video content, 3D modelling, CAD work and software development all live on one canvas.

It is built for teams that currently move assets between half a dozen specialised applications and lose context every time they switch.

What it is

A project, not a pile of export folders. Assets, sequences, 3D scenes and automation scripts can reference each other directly. The same file system and permission model used by the rest of Ocalt applies, so creative work is not isolated from the rest of the platform.

Forge is also an automation surface. Finished work can be handed off, transcoded, watermarked, published or scheduled without leaving the same product — because MEDIA, GRAPHIC, FILE SHARE and SCHEDULE are already in the language.

What it does

• Visual design, motion, modelling and code in one environment.
• Presentation tools and productivity features so a deck, a site and a render can share a project.
• Keeps timelines, models and scripts in one place so a change in one domain remains visible to the others.
• Runs heavy work on the Ocalt server. Renders, transcodes and tessellation execute there, and the canvas streams back only what it needs to show.
• Publishes: a subdomain, a shared link, an API endpoint, an email. The pipeline ends where the audience is.

How it works

Everything is organised around a shared project model. Media is a first-class type in OcaltQL: images, video and audio are values the language understands. Resize, crop, watermark, transcode, trim, extract a frame, stitch a timeline — without shelling out to a filter graph you have to memorise.

3D and CAD sit on the same foundation as the rest of the language. A solid, a mesh, a sketch and a scene are types. Tessellate a solid for a viewport, or discretize it for analysis, with verbs rather than a second product.

Getting started

1. Open forge.ocalt.com and create a project. Put a source file in the namespace — upload, FILE WRITE, or DIRECTIVE DOWNLOAD off a machine.
2. Transform it in the canvas, or from a script with GRAPHIC / MEDIA.
3. Publish with FILE SHARE or by putting the output on a subdomain.
4. When the same job will run again at midnight, wrap the working script in a SCHEDULE or CRON.

MEDIA LOAD "/mounted/raw/episode.mov" SET ?clip
AFTER MEDIA ?clip TRIM FROM "00:00:12" TO "00:04:30" SET ?cut
AFTER NEW TRANSCODE STREAM FROM ?cut QUALITY "1080p" TO "/root/out/episode.mp4"
AFTER IMAGE LOAD "/mounted/raw/thumb.png" SET ?thumb
AFTER GRAPHIC ?thumb RESIZE WIDTH 1280 SET ?thumb
AFTER FILE SHARE "/root/out/episode.mp4" SET ?link
AFTER NOTIFICATION "episode ready: " & ?link("url")

Disciplines on one canvas

Who it is for

Creators, agencies, product teams and technical teams that are tired of the constant hand-off between specialised tools. Solo operators who want a pipeline that runs at midnight. Studios that want a render to be a queued job rather than a person who remembers to press Export.

Related products

FAQ

Does Forge replace Blender / Premiere / Figma?

It is the unified canvas and the automation around it. Specialised tools can still produce sources; Forge is where those sources stop being stranded exports. Use both if a discipline is already deep on another desk.

Where do large media files sit?

On root or mounted storage. Mounted storage sizes follow the plan. Keep raw on a machine Ocaltio has mounted; keep deliverables in /root/out if they must survive the machine going offline.