Generato Generato
Template-based asset generation

Design once.
Populate at scale.

Generato turns one template into a batch of print-ready and digital assets. Pick the mode your team already works in — a browser CMS with a full review workflow, or a standalone Figma plugin with AI-assisted bindings.

Open the dashboard → See the Figma plugin
Fully open-source render stack PDF/X-4 preflight Multi-tenant SaaS or single-tenant on-prem
Web mode studio.generato.app

Digital + print, no Figma required

Templates authored and edited in the browser. Content lives in a structured CMS. A pipeline renders print-ready PDF/X-4 and digital formats (PNG, JPG, WEBP) at batch scale, with a review + approval workflow.

  • — Browser-based template authoring (no Figma file needed)
  • — Role-based: editors, reviewers, approvers, producers
  • — Batch rendering with inline PDF annotation + approvals
  • — Print track: CMYK / ICC (FOGRA39, GRACoL), crop + bleed, veraPDF-validated PDF/X-4
  • — Runs multi-tenant on Railway or single-tenant on-prem from the same image
Open dashboard →
Figma mode Figma Community plugin

Stay in Figma. Generate at scale.

A standalone plugin for designers who want the design file to remain the source of truth. Tag layers once, pull data from Google Sheets, CSV, XLSX, or the built-in form, and the plugin clones the template per row and expands repeaters — no server, no CMS, no account.

  • — Everything runs inside Figma — nothing leaves your file
  • — Data sources: Google Sheets, CSV, XLSX, or in-plugin form
  • — Repeaters for arrays (practice areas, bullet lists, cards)
  • — AI built in — suggest bindings, generate a starter CSV, or create a design from a brief (see below)
  • — Export via Figma's native PDF / PNG / JPG flow
Figma Community — relisting soon Republishing from [email protected]
New · in the Figma plugin

AI that speeds up the tedious parts

Bring your own API key — Generato calls the provider directly from the plugin iframe. No keys ever touch a Generato server, no usage goes through us. You see a token estimate and dollar cost before every call.

Supported providers
Anthropic OpenAI OpenRouter Gemini DeepSeek xAI (Grok) Moonshot (Kimi) zAi (GLM)
01 · Suggest bindings

Point at a frame, get tagged layers

The plugin sends a snapshot of the selected template frame (layer names, sizes, a bit of context) and gets back a suggested binding path for every layer. Review, uncheck the ones you don't want, and apply.

02 · Starter CSV

Get a realistic data sample

Given the bindings already tagged in the frame, the plugin writes a CSV header and three plausible sample rows. Paste it into Sheets, tweak, and you're ready to generate.

03 · Design from a brief

Describe it, drop it on the canvas

Type a short description — "A4 partner profile, headshot top-right, 3-paragraph bio, practice-areas repeater at the bottom" — and the plugin builds a new Figma frame with layers already tagged with bindings.

Keys are stored per-user on your machine via Figma's clientStorage. Pricing is shown per-provider, per-model before every call.

How it works

Web mode Browser + CMS
  1. 01
    Author a template
    Build or import a template in the CMS. Fields are typed — text, rich text, images, arrays, references.
  2. 02
    Fill content
    Editors work in Payload with draft/publish, versioning, and role-scoped access. Assets get DPI + colour-space metadata on upload.
  3. 03
    Render a batch
    Producers queue a batch. The pipeline composes each document, renders digital previews, and caches them in S3-compatible storage.
  4. 04
    Review, approve, print
    Reviewers annotate inline. On approval, the print track runs: Ghostscript converts to CMYK, embeds FOGRA39, veraPDF validates PDF/X-4, and the zipped output ships.
Figma mode In-file, no server
  1. 01
    Bind
    Select a layer, pick a binding path (partner.name, partner.practiceAreas[].label). Metadata is stored on the layer itself, so renames don't break anything.
  2. 02
    Load data
    CSV upload, XLSX upload, Google Sheets share link, or the built-in form. Or use AI to generate a starter CSV that matches your bindings.
  3. 03
    Map
    The plugin auto-matches columns to bindings. Review, tweak, done.
  4. 04
    Generate & export
    The plugin clones the frame per row, substitutes text, fills images, expands repeaters, and lays results out on a new page. Export with Figma's native PDF / PNG / JPG.

Who picks which mode

The two modes are deliberately independent — same brand, same author (Eutin Warren), different trade-offs. Pick by team, not by feature count.

Pick web mode if…
  • — You need print-ready PDF/X-4 alongside digital output.
  • — Editors and reviewers are non-designers who live in the browser.
  • — You want approval workflows, versioning, and role-scoped access.
  • — You're running many assets across many people (partner profiles, sector decks, credentials, newsletters).
  • — You want to host it inside your own infrastructure (on-prem Docker).
Pick Figma mode if…
  • — Your design system and typography already live in Figma.
  • — Output is digital-first (social, presentation exports, mailers).
  • — You want zero infrastructure — no server, no login, no billing.
  • — One designer drives generation locally, data lives in a spreadsheet.
  • — You want an AI assistant for the setup without handing anyone your data.

One codebase, two shapes

The web product ships in two deployment modes from the same source — so you can start on the hosted offering and move in-house later without a rewrite.

Hosted

Multi-tenant SaaS

Sign up at studio.generato.app. One deployment serves many tenants with per-tenant brand config, font vaults, and approved palettes. Runs on Railway with Postgres, S3-compatible storage, and Redis.

On-prem

Single-tenant inside your infra

Delivered as a Docker Compose bundle. Your Postgres, your S3-compatible store, your Redis — or the bundled ones. No cross-tenant surface in the UI, everything scoped to one fixed tenant. Identical migrations to SaaS.

What we won't do

No commercial render lock-in

The entire render stack — Paged.js, Chromium, Ghostscript, veraPDF, pdfcpu — is open source. No per-seat fees, no InDesign Server, no vendor padlock on your output.

No WYSIWYG design editor in the review app

Three sources of truth, strictly separated. Figma or the template owns design. The CMS owns content. The review app owns decisions. Edit buttons deep-link to the right system.

No data flowing through us in Figma mode

The Figma plugin is standalone. Your data stays in your Figma file and your spreadsheet. Even AI calls go directly from the plugin to the provider with your own API key.