Slate

Slate turns images, audio, fonts and video you already own into a finished MP4. You send it a recipe, a short JSON description of the video you want, and it renders the video with ffmpeg on a queue in your own Laravel Cloud account. When the run finishes, Slate gives you one signed download URL for the result, which stays in your own bucket.

Slate is an API with a small settings area for people. It has no editor, no template library and no timeline. Your own application uploads the media, builds the recipe and collects the result.

What it renders

Two recipes exist:

• delivery takes an ordered list of pages. Each page is an image and an audio track, with optional word-by-word captions. Pages are joined with one-second cross-fades.
• highlights takes one video source and a list of time ranges, cuts them out and joins them into a single video.

You never send ffmpeg arguments. Slate accepts named fields with typed, validated values and builds the command line itself. This is a security boundary: ffmpeg can read and write files and URLs, so an API that passed arguments through would let a caller read the server's disk.

How it fits with Scalpels

Scalpels forks Slate into your GitHub account and creates the database, managed queue, bucket and scheduler on your Laravel Cloud account. It also bakes a pinned ffmpeg build into every deploy. Slate is not a provider app and has no client package. Anything that can send JSON over HTTPS and download from a signed URL can call it.

Slate is Experimental in the Scalpels catalog. Only supporter and partner teams can install it through Scalpels.

Pages

• Getting started: install Slate, what the install creates, signing in and a first check.
• API credentials: the installation reference, issuing a bearer credential, and rotating or revoking it.
• Sources: uploading media or pointing Slate at a URL, source statuses, and the checks every source goes through.
• Recipes: the delivery and highlights formats field by field.
• Runs and results: submitting a run safely, following its status, downloading the result and receiving a signed webhook.
• MCP tools: the five tools your agent can call through Scalpels.
• Configuration: the one value you can choose, the fixed limits, and the maintenance commands.
• Troubleshooting: 401s, rejected sources, failed uploads and stalled runs.

Want a branded address for this deployment? Use your own domain.