Skip to content

The company blog, published by the people who write it

Teams that publish often and have no developer to borrow.

Free to start, no card. You can export your posts at any time, on every plan.

The post is ready on Monday. Publishing it takes a ticket, a developer's afternoon and a deploy window, so it goes out on Friday, after the news it was about.

Hand everyone the keys to the main site instead, and one bad save can break the pricing page.

Typoza keeps the blog apart from the rest of your site. The people who write it publish it themselves, and nothing they touch reaches your product pages.

What you need

  • Publish without engineering

    The blog runs on its own subdomain, or on your domain with a paid plan, apart from your main site. Publishing a post triggers no deploy and changes nothing else.

  • Roles that match who does what

    Owners and admins run the workspace. An author writes and publishes their own posts, an editor publishes anyone's, a reviewer comments without editing, and a marketer runs the newsletter without seeing any draft.

  • Review inside the tool

    Sending a post for review changes its status and notifies the people who review. They comment on passages in a read-only editor, and a preview link lets someone outside the team read the draft.

  • Know what gets read

    You see views, visitors, the most-read posts and where readers come from, over the period you pick, and can export them as CSV or JSON. A visit sets no cookie, so the public site needs no consent banner.

  • AI with a budget

    You pay for writing help in credits, and each workspace shows its own balance. The owner can cap what each member spends in a month, and an admin can switch AI off for the whole workspace.

  • Paperwork that holds up

    Each workspace gets its own invoices, in euros, with VAT set out and your company's VAT number once you add it. If the blog moves one day, the export carries every post in Markdown and JSON.

What Typoza does not do

Better to read it here than to find out after three posts. If one of these is a dealbreaker for you, do not sign up.

  • Review is a step a writer chooses. An author can publish their own post without it, and no role writes without being able to publish; if every post needs sign-off, your team has to hold that rule itself.
  • A team needs a paid plan: on the free plan, the workspace holds its owner alone.
  • No sign-in through a corporate directory. Each member signs in with a passkey, a password with an optional second factor, an email link or GitHub.
  • Review has one stage. If a post goes through legal and then management, run that circuit outside the tool.
  • Pages use the same editor and layout as posts. A landing page with its own sections needs a site builder.
  • A workspace publishes in one language, and nothing here translates a post. The dashboard itself is in French.

The post you keep putting off

Write its first paragraph today. The post stays a draft until you publish it, and no reader sees it before then.

Free to start, no card. You can export your posts at any time, on every plan.

The other use cases