Anjin Design
Start free

Every client on brand.
At any volume.

Design a template once in a real design editor. Then produce thousands of images from it — by API, by AI agent, or by filling in a form.

What comes out is pixel-identical to what your designer made. Not a rebuild in someone else’s renderer. The same engine.

Start free →See how it works30 credits free. No card. No watermark.
Pixel-identical output
verified at SSIM 1.00000
Import your Figma file
keep the design you already have
No forced upgrades
top up any time
Built for agents
REST, MCP and CLI

The problem

The bottleneck was never the design. It was the two hundredth version of it.

Your designer builds something good. Then the requests start. The same post in four sizes. The same ad with nine headline variants. The same thumbnail every week for a year.

None of it is design work. All of it lands on the designer — or worse, it doesn’t, and someone rebuilds it in a consumer tool at eleven at night and the kerning is wrong and the client notices.

You don’t have a design problem. You have a production problem.

How it works

Three steps. The first happens once.

  1. 01

    Design it once

    Build your template in the editor — or import the .fig you already have. Real type control, real layout, real gradients. Not a form builder.

  2. 02

    Mark what changes

    Click a headline, mark it as a text slot. Click a photo, mark it as an image slot. Everything you don't mark is locked. That is the brand safety.

  3. 03

    Produce as many as you need

    Fill the slots — from the dashboard, from the API, from a spreadsheet, or from an AI agent. Every render is on brand, because the parts that make it on-brand were never editable.

Why it matches

Other tools rebuild your design. We render it.

Every other template API takes your design, re-implements it in their own rendering engine, and hopes it matches. Mostly it nearly does. Then a font weight resolves differently, a line wraps early, a gradient bands — and you find out after it has gone to a client.

Anjin runs one engine in two homes. The renderer inside the editor and the renderer behind the API are the same engine, running the same file. Parity isn’t a promise we test for. It’s a property of how the thing is built.

Structural similarity

1.00000

A perfect match between what the editor shows and what the API returns. Measured, not asserted.

What people make

One template. Everything downstream of it.

Social, at calendar scale

A month of posts across every channel, sized right for each.

YouTube thumbnails

The channel look, every week, without opening a design tool.

Paid ad variants

Every headline × image permutation, ready before the brief is signed off.

Presentations

On-brand slide graphics nobody has to redesign.

Product imagery

One design, every size and aspect ratio you ship.

Whatever's next

It's a template and an API call.

Three ways in

However your team actually works.

Your dashboard

Fill in the fields, get the image. No code. This is what most of your team will use.

Your codebase

One call, one on-brand image. Batch endpoint for volume, signed webhooks, permanent asset URLs.

Your agents

Anjin speaks MCP. An agent can discover your templates and render from them — and cannot produce off-brand output. Works with Claude Code today.

curl -X POST https://api.anjin.design/v1/renders \
  -H "Authorization: Bearer $ANJIN_API_KEY" \
  -d '{"template":"acme_instagram_1080x1350",
       "modifications":[{"name":"headline","text":"Launch day"}]}'

Ask, and it's produced

A brief in. On-brand files out.

Anjin speaks MCP, so an agent can discover your templates, read what each one accepts, and render a whole campaign into a folder. It cannot invent a colour, reach for the wrong photo, or move the logo — those were never in its control.

Assistant

Make the Q3 launch assets for Northwind — four headlines across Instagram, story and LinkedIn.

anjin-design · list_templates3 published templates
anjin-design · get_template_schemaheadline · hero_image · brand_color
anjin-design · render_batch12 renders queued

Done — 12 on-brand assets rendered and saved to Renders / Q3 Launch.

Renders / Q3 Launch
NORTHWIND

Built for Q3

northwind_ig_1080x1350

NORTHWIND
PRODUCT

Ships faster

northwind_story_1080x1920

NORTHWIND

Now in beta

NEWS

northwind_li_1200x627

NORTHWIND

One platform

LAUNCH

northwind_ig_1080x1080

NORTHWIND

Built for Q3

LAUNCH

northwind_story_1080x1920

NORTHWIND

2×

Ships faster

northwind_li_1200x627

Same template. Different copy, format and treatment. Every one on brand.

Part of something bigger, when you need it

One surface of the Anjin marketing OS.

Run Anjin Design with Anjin Media, Anjin Social and Anjin Marketing and you have a full organic content machine — brand guidelines enforced at the point of production, your content archive feeding it, distribution across every channel, orchestrated rather than assembled by hand.

Use Anjin Design entirely on its own. The rest is there when you want it.

Explore the Anjin OS →

Design it once. Produce it forever.

Start free →

30 credits. No card. No watermark. Nothing to uninstall if you hate it.