Font engine for website builders
Every site, its own typeface.
Let every site owner make their own typeface.
Sites stop looking like their template, and your platform offers what no font menu can.
Set in Arc
30 days, no card
Same template,
same few fonts.
Sites on a template share the handful of fonts it ships with, so a bakery and a law firm end up looking alike.
- The font menu
- The same short list every other site on your platform picks from, and every other platform too.
- A custom typeface
- A design project with a type designer, out of reach for almost every small business.
- An uploaded font
- Missing accents and figures that break the template, and a web licence the owner may not hold.
Shaped by
its owner.
Owners make it beside their own page, in minutes, with no type design skill.
- Recognisable
- Their site stops looking like the template and starts looking like their brand.
- Their own
- Made by them, for their brand, and you can let them use it commercially anywhere.
- Complete
- 271 characters: capitals, accents, figures and symbols, all drawn in one hand.
- Quick
- They turn a few controls and watch every letter on the page follow.
Heading font
Try it: these sliders turn the real engine, as your editor's would.
Beyond any
font menu.
Any platform can add fonts to its menu. Letting every owner make their own is what sets yours apart.
- Stand apart
- Your competitors offer the same font menu you do. A font of their own is a reason to build on your platform instead.
- Charge for it
- Put it on a premium plan or sell it as an add-on. The Engine License covers it for your paying customers.
- A reason to stay
- Their brand's font lives in your editor, beside their site, and that's where they come back to change it.
- Templates go further
- One layout becomes as many looks as there are owners, without designing another template.
- Licensing, settled
- You decide how owners use their fonts, from full commercial rights to your own terms, in every file. No royalties to us.
- Nothing to host
- No type designers, no font engineering, and no AI model or GPU to run: the SDK draws and makes every font.
One template,
five brands.
The layout and the words stay the same. Only the font changes, and each site reads as its owner's.
It runs in
your editor.
Published sites only get a font file, so nothing changes for their speed or their visitors.
- In your editor
- The JavaScript SDK, in the browser, with a few of its 106 parameters as your own controls.
- With the site
- A recipe: a few numbers, saved on the site's record.
- On publish
- One WOFF2 file of about 20 KB, served with the site's CSS like any other asset.
- On every visit
- Only that file: no engine, no script and no call to us.
Try it in
your editor.
Free first, in your own code. Then a pilot with real site owners.
- Free evaluation
- Free for 30 days, with no card. The SDK in your own development and testing, before your live product.
- Pilot
- $500 for 60 days. Go live with your real users before you commit to a year.
- SDK licences
- Yearly, for your live product, side by side on the pricing page.
Good to know
Because type is most of what makes a site look like a brand rather than a template. Today they pick from the same menu as everyone else, or commission a custom typeface few small businesses can afford. A font they make in your editor looks like them, and you can let them use it on their signs, menus and posts as well as their site.
Yes. The Engine License lets you build the engine into your product for your paying customers, so you can put it on a premium plan, sell it as an add-on or include it for everyone: the pricing is yours. What you can't do is sell the engine itself, or offer it as a font service of its own.
No. The engine draws every letter from its parameters, with accents, figures, spacing and kerning, so a font is complete whatever numbers an owner picks. You choose which few controls to show, and owners turn them beside their page. It's procedural drawing code, not AI.
The one you choose. You decide how your site owners may use their fonts, from full commercial rights to narrower terms of your own, such as use only on your platform, and write it into your terms and into every file: the SDK sets each font's licence text and link, copyright, vendor id and embedding setting. If you set nothing, owners get full commercial rights. Either way, there are no royalties to us.
Under the Engine License, the rights to a font made in your product are yours, as the platform, and you decide how its site owner may use it: full commercial rights, or terms of your own. There are no royalties to us, and those rights last after your licence ends. Nobody owns a font exclusively, though: the same numbers always draw the same letters, so another site could arrive at the same font. A font's name is the owner's to clear.
That's for your terms to say. You can let owners take their font with them or keep it to your platform; if you set nothing, they get full commercial rights and can go on using it elsewhere. Whether you hand them the file, as a WOFF2 for the web or a TTF to install, is up to you too.
271 Latin characters with accents: the alphabet that Western and Central Europe, the Baltics, Turkey, Azerbaijan, Iceland and Wales need, plus figures, punctuation and symbols. No other scripts, and no Vietnamese, so give a site a fallback font for those, and check its text with engine.coverage().
A font panel in your editor, and a place to keep a few numbers with each site. The JavaScript SDK draws the letters as owners turn your controls and compiles the font when they publish. The web docs show each step, and the free evaluation lets you try it in your own code first.
No. The engine loads only in your editor: 2 MB over the wire with Brotli, best fetched when someone opens the font panel. A published site serves one WOFF2 file of about 20 KB, with no script and no call to us.
Start with one site.
Evaluate the SDK free for 30 days in your own editor, then pilot it with real site owners.