Nebula Sans: what a SaaS gains from owning its font

Have you ever paid for something in your product without knowing you were paying for it? Fonts are the classic example. They live on every screen, every button, every invoice your system sends out. And almost nobody knows who owns them, what they cost, or what happens if the vendor changes the rules. Nebula Sans was born from exactly that question inside a SaaS. And the answer they came up with applies to much more than typography.

What Nebula Sans is, in one sentence

It's a free, open source font made by Uniweb, a Canadian company that sells a website platform for universities. They are not a type foundry. They are an ordinary SaaS, with customers, support and a roadmap. Even so, they decided to own their font.

The base is Source Sans 3, from Adobe, which was already open. Uniweb took that starting point, tuned the design for on-screen reading, handled the variable weight and language coverage, and published everything under the SIL Open Font License. Anyone can use, modify and distribute it. Including you.

The important detail is not the shape of the letters. It's the motivation. They wanted a font that worked well in their product and that nobody could take away from them later.

Why a SaaS cares about fonts

It sounds trivial until you look at the contract. Commercial web fonts are usually licensed per domain, per monthly pageviews, or per number of "installations". For a corporate website, that's manageable. For a SaaS, it's a time bomb.

Think about Uniweb's case. Every university customer has its own domain. Every domain gets thousands of visits. If the font is licensed per pageview or per domain, the cost grows along with the product's success. You close a new customer and the foundry's bill goes up. It's the kind of cost nobody puts in the spreadsheet when pricing the plan.

Then there's the control problem:

• You can't change the design. Found the digit 1 confusing next to a lowercase l in a pricing table? Too bad.
• You can't redistribute. A customer wants the same font in the PDF they export from the system? That depends on another license.
• The vendor can change the price, the terms, or simply discontinue the family.

An open font solves all three at once. Zero cost per visit, the right to modify, and the guarantee that the file stays yours forever.

Depending on third parties is normal. Depending without knowing is not

I'm not saying every SaaS needs to create a font. That would be madness. I'm saying every SaaS needs to know who it depends on and what each dependency costs when the business grows.

Fonts are just the most visible example. The same logic applies to:

• The transactional email service that charges per message sent.
• The embedded map that charges per load.
• The AI API that charges per token and changes prices every quarter.
• The chart component with a "per developer" license that becomes "per end user" at renewal.

Each of these items has a small price today. Put five of them together, multiply by the growth you expect over the next two years, and the product's margin disappears. I've seen a company with a $99 per month plan where third-party dependencies alone ate $40 per customer. The owner didn't know. They found out when raising investment.

Every cost that grows with usage needs to be in your spreadsheet before it shows up on your invoice.

Uniweb did the math early. They concluded that one week of work on an open font came out cheaper than years of licensing. And, as a bonus, they gained a tool they can adjust whenever the product calls for it.

What "made for screens" really changes

Here comes the part that interests me as a designer. Nebula Sans is not just Source Sans with a different name. The adjustments target exactly the problems that show up in software interfaces:

Small sizes. In a SaaS, a lot of information lives at 12 or 13 pixels: field labels, table captions, help text. Fonts designed for paper turn into a blur at that size. A font tuned for screens opens up the inner spaces of the letters a bit and lets everything breathe.

Variable weight. Instead of loading six files (light, regular, medium, bold and so on), you load one file that contains every weight. Fewer requests, faster page. For a SaaS where the user opens 200 screens a day, that gets noticed.

Numbers that behave. In dashboards, tables and financial reports, numbers need the same width so the columns line up. It's called tabular figures. It's the kind of feature nobody notices when it exists and everybody notices when it's missing.

Language coverage. Latin, Greek and Cyrillic in the same file. If you have a customer in Portugal and another in Greece, the product doesn't change its face between them.

None of this is glamorous. But all of it is what separates a product that "looks professional" from one that "looks like a weekend project", even when the code behind it is identical.

How to apply this to your business today

You don't need to fork a font. You need half an hour with a spreadsheet. I suggest three steps:

1. List everything your product uses that isn't yours. Fonts, icons, paid libraries, APIs, email services, maps, authentication. Note the billing model for each: flat, per user, per usage.
2. Simulate the cost with twice as many customers. If any item doubles along with it, it deserves attention. If any item triples, it deserves an alternative.
3. For each expensive item, ask: is there an open version that's good enough? For fonts, there almost always is. For email, maps and charts, often too.

When it comes to fonts, my opinion is direct: for 95% of SaaS products, there is no reason to pay for a font license. Nebula Sans, Inter, Source Sans, IBM Plex. All free, all excellent on screen, all with the right to modify. Paying for a font in a digital product today is like paying for bottled water at a restaurant that serves filtered water for free. It can make sense, but you need to know why.

What the Nebula Sans story teaches about product

What catches my attention is not that Uniweb made a font. It's that a mid-sized company looked at a detail almost everyone ignores, did the math, and acted before it became a problem. And then opened the result for anyone to use.

That's product maturity. It's not about typography, it's about knowing where your business is exposed and reducing the exposure while it's cheap.

If you're building or reworking a SaaS and want someone who looks at the whole product, from the screen design to the hidden cost of each dependency, that's the kind of work I do. Learn a bit more about me and how I work.

Have you ever paid for something in your product without knowing you were paying?

Fonts are the classic example. They live on every screen, every button, every invoice. And almost nobody knows who owns them, what they cost, or what happens when the vendor changes the rules.

Nebula Sans was born from that: a Canadian SaaS did the math, saw that licensing per domain or per pageview grows along with success, and decided to own an open font instead. One week of work versus years of invoices.

The lesson applies to transactional email, maps, AI APIs, chart components. I've seen a $99 plan where $40 went to dependencies the owner didn't even know about.

Every cost that grows with usage needs to be in your spreadsheet before it shows up on your invoice.

I wrote about what Nebula Sans teaches about product and how to do this math in half an hour. Link in the comments.

#SaaS #ProductDesign #Typography #Product #OpenSource