Hype StackHypeStack

Use case

Freelance Invoicing Software

Invoicing software does not get you paid faster because it makes prettier invoices. It gets you paid faster because it chases, and chasing is the part freelancers avoid.

For a freelancer, invoicing is where the business actually happens. Everything else can be improvised; this cannot, because it is the point where work becomes money and where the tax authority takes an interest.

We sell source code you clone and run yourself, so there is nothing hosted here. For freelance invoicing the free products are genuinely good, and the useful thing this page can do is say what to look for and where free stops.

The free options are strong in this category

Wave, Zoho Invoice, Square Invoices, and Invoice Ninja all appear in this search, and several of them are free for the volume a solo freelancer produces. The business models differ and that is worth understanding rather than ignoring: some are free because they charge on card payments, some because invoicing is the entry point to paid accounting, and one is open source and self-hostable.

That means comparing on total cost rather than the headline. If clients pay by card, the processing fee is the real price, and it is charged either way.

What actually gets you paid

Features ranked by effect on cash, not on appearance

  • Automatic payment remindersA polite email before the due date, on the due date, and at intervals afterwards, sent without you deciding to send it. This has more effect on payment times than everything else combined, because it removes the awkwardness that makes freelancers delay.
  • Pay from the invoiceA link that takes payment immediately rather than a bank transfer the client has to arrange. Reduces friction on the client's side, at the cost of a processing fee.
  • Clear payment terms on the documentDue date, not just issue date, and what happens if it is late. Terms that exist in your contract but not on the invoice are terms nobody sees at the moment of paying.
  • Recurring invoices for retainersIf any client pays monthly, this removes a recurring administrative task and the risk of forgetting a month, which happens more often than freelancers admit.
  • Deposits and partial paymentsTaking a percentage up front changes your cash position and filters out clients who were never going to pay. The tool needs to represent a partly paid invoice rather than treating it as unpaid.

Reminders and a payment link are the two that move the numbers. Templates and logos do not.

The parts that are about tax, not invoicing

This is where free tools differ most, and where getting it wrong costs more than the subscription.

Sequential numbering matters in many jurisdictions: invoice numbers should not have gaps or repeat, because that is what makes the record auditable. Most tools handle this, and it is worth confirming rather than assuming, particularly if you ever delete a draft.

Sales tax or VAT handling depends on where you and your client are, and cross-border rules for services are their own subject. If you are registered, the invoice has to carry the right identifiers and the right treatment, and a tool built for a single country may not express it.

Currency is the third. Invoicing in a currency you do not bank in means the amount you receive differs from the amount invoiced, and how the tool records that difference affects your books.

None of these are reasons to pay more; they are reasons to check before choosing.

Where invoicing meets time tracking

For hourly work the two are one workflow, and the friction is entirely in the join. If billable time does not become invoice lines without retyping, that retyping happens every month permanently.

The practical advice is to choose whichever tool covers both if you bill hourly, even if each half is slightly weaker than a specialist alternative. The integration is worth more than either feature.

When a freelancer builds

Not an invoicing tool. Tax rules, numbering, and payment integrations are a lot of surface for something available free, and mistakes here have consequences that a broken side project does not.

The case that appears is invoicing inside a product: an agency platform where clients are billed for work tracked in the system, a marketplace paying out to suppliers, a vertical tool where invoicing is part of the workflow. In those, the invoice is generated from data the system already holds and a standalone tool cannot see it.

What you would start from here

There is no invoicing in this stack. No invoices, no numbering, no tax handling, no reminders, no payment collection against an invoice, and no accounting export.

What the Better Studio template provides is the application around it: organizations as the tenancy boundary, roles and invitations, a Hono backend with Prisma and Kysely on Postgres, an admin app, and Stripe billing for subscription revenue. That distinction matters here: the billing pack handles subscriptions to your product, which is not the same as issuing an invoice to a client for forty hours of work.

For that second thing, integrate an invoicing or accounting provider rather than implementing it. Generate the invoice from your own data and let their system own numbering, tax, and the audit trail. That keeps the regulated part with somebody whose job it is.

If you are a freelancer invoicing clients, use one of the free tools above and turn the reminders on. The packs below are for the case where invoicing is a feature of something you are building.

Hype Stack

What is Hype Stack?

Every product starts with the same month of work nobody pays you for: sign-up and login, teams and permissions, taking payments, notifications, an admin panel to run the business. Hype Stack is that month, already built and tested. Start from the free open-source app, add the pieces you need with one command, and keep going on the part that is actually your idea.

Everything lands as real code in your own repository, so there is nothing to rent and nothing anyone can switch off. For the engineers: React 19, Hono, Postgres, and a desktop build, typed end to end.

See it running

Templates are curated project starters built on this stack: a layout, feature packs, a custom theme, and bonus pages. The previews below are recordings of the real apps.

Packs in this stack

Every pack ships real source code: frontend, backend, and admin surfaces where the feature needs them. The ones this stack installs come first; the rest can be composed in later.

Two ways to install features

Same features underneath, different starting point. Either command resolves what the packs depend on, copies the source into your repository, and merges the Prisma schema.

Ready-made

Take a template

A landing page, a design system, a themed layout, and the features already wired into it. Rebrand it, put your product in the middle, ship.

$npx @hype-stack/cli template
Browse templates
From scratch

$ hype-stack compose

AuthPayments

Compose your own design

Your design and your choices, without rebuilding auth, billing, or notifications. Tick the packs you want and the CLI wires them into the open-source starter.

$npx @hype-stack/cli compose
Browse packs

Questions, answered

Wave, Zoho Invoice, Square Invoices, and Invoice Ninja all appear for this, and several are free at solo freelance volume. The business models differ: some charge on card payments, some use invoicing as an entry point to paid accounting, and one is open source and self-hostable. Compare total cost, since a processing fee is charged either way.

More stacks

Turn your ideas into
Real applications.

Start free and own every line you ship. When you want more, one All-Access license unlocks every premium pack and template for a year.

All premium packsEvery template12 months of updates
Get All-Access