Every brand kit, its own typeface.

Because the font is on everything their brand makes, and today it's the one part of their kit they share with everyone else. A typeface of their own makes their posts, slides and packaging look like them rather than the template, and making it is a few minutes with controls, not a design project.

Yes. The Engine License covers building it into your product for your paying customers, so you can offer a brand typeface as a premium feature, in a paid tier or as an add-on. What you charge is up to you.

No. The engine keeps all 271 characters consistent whatever your customers choose, so every setting of the controls gives a complete font. Your team builds the controls, in your own design, from a catalog with every parameter's range and default. If you'd rather have Typomat's own dials redrawn in your design, that's White-label, built with you as a project.

The rights to the fonts made in your product go to you, under the Engine License, and you decide how your customers may use them. Pass on full commercial rights, or set narrower terms of your own, such as use inside your product only, and write them into your terms and each font's licence text and embedding setting. If you set nothing, your customers get the full rights. There are no royalties to Typomat either way, and it carries on after your licence ends. The fonts aren't exclusive: the same settings draw the same letters, so someone else could arrive at the same font.

Whatever you set. The SDK writes your own metadata into every font it makes: the licence text and a link to it, copyright, trademark, designer, your vendor ID and the embedding setting (installable, editable, preview or restricted). So each file says where it came from and the terms you give your customers.

Yes, if your terms allow it: they can set their wordmark in it and convert it to outlines, as they would with any font they use commercially. Clearing a logo or a font's name as a trademark stays theirs to do: the licence doesn't do that for them.

If you let them export their font, it's a real TTF, OTF, WOFF or WOFF2 file that keeps working in any tool, on the terms you gave them. Whether and when they can export is your choice.

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 keep a fallback font for those.

No. It's procedural drawing code: the same settings always draw the same letters, there's no model and no training data behind it, and nothing to host on a GPU.

Yes. The same engine comes as a JavaScript package for the web and Node, and as a native Swift package for iPhone, iPad and Mac. One recipe gives the same font in both, so a brand made on the web opens the same in your app.