What is Indie Hacker?
A person who builds and runs an online business, usually software, on their own or with a tiny team, funded by revenue rather than venture capital.
Definition
An indie hacker is someone who builds a profitable online business independently, typically alone or with one or two partners, and usually without outside investment. The business is often a software product such as a SaaS app, a browser extension, a mobile app, an API, a template or a digital product, but newsletters, communities, courses and niche marketplaces count too. The goal is usually independence: a business that pays the founder's bills, gives them control over their time and work, and grows from revenue rather than from funding rounds. Indie hacking is the practice of building such a business. The term was popularised by Indie Hackers, an online community and podcast founded by Courtland Allen in 2016, where founders share revenue numbers, growth tactics and lessons from their projects. The site was acquired by Stripe in 2017 and grew into one of the best-known gathering places for bootstrapped founders. Today the culture also lives on X (Twitter), Reddit, Hacker News 'Show HN' posts, Product Hunt launches and many smaller communities. Indie hackers share a recognisable playbook. They start small, often with a micro-SaaS that solves one specific problem for a narrow audience, and validate demand early with a landing page, waiting list or minimum viable product. They charge from day one, track monthly recurring revenue (MRR), and favour simple, low-cost infrastructure such as managed hosting, serverless platforms, backend-as-a-service tools and payment providers or merchant-of-record services that handle global sales tax. Many build in public, sharing progress, revenue and setbacks openly, which doubles as marketing. Distribution is usually the hardest part, so successful indie hackers invest in SEO, content, communities, partnerships, directories and launch platforms as much as in code. Increasingly, AI coding assistants let a single person ship products that once needed a small team. Indie hacker vs startup founder: a venture-backed startup founder raises money to grow fast, hires a team and aims for a large exit or very high scale, accepting high risk and outside control. An indie hacker optimises for profitability, autonomy and sustainable income, so a business with modest revenue and no employees can be a complete success. The two overlap, since some indie projects later raise money, and some founders bootstrap first by choice. Indie hacker vs solopreneur: solopreneur is a broader term for anyone running a one-person business, including consultants and freelancers; indie hacker usually implies building a product rather than selling hours, and a strong online and technical flavour. Well-known examples include Pieter Levels, who built products such as Nomad List and Remote OK largely on his own and publicly shared their revenue, and countless smaller micro-SaaS founders earning a living from tools such as form builders, analytics apps, screenshot APIs or niche job boards. Common risks include building something nobody wants, underestimating marketing, platform dependency on a single marketplace or API, burnout from doing every job alone, and inconsistent income in the early months, which is why many indie hackers start their projects alongside a job or freelance work.
When to Use Indie Hacker
Indie hacking suits builders who want ownership and flexibility more than hypergrowth, and who are willing to learn marketing, sales, support and finance alongside product work. Start by picking a narrow problem you understand, ideally one you have experienced yourself or seen repeatedly in a community you belong to, and validate that people will pay before building much. Keep scope tiny, launch quickly, and charge early, because revenue is the clearest validation signal. Treat distribution as part of the product from day one: SEO-friendly content, comparison and alternative pages, directories, integrations with platforms your customers already use, and genuine participation in communities. Use boring, cheap infrastructure so the business stays profitable at small scale. Many people indie hack on the side of a full-time job to reduce financial risk, so check your employment contract for conflict-of-interest and IP clauses first. If a product starts growing faster than one person can handle, you can still hire, raise money or sell the business; indie and venture paths are not mutually exclusive.
Indie Hacker in Practice
- A typical indie hacker path: a developer notices freelancers struggle to chase late invoices, builds a small SaaS that sends automatic reminders in four weekends, launches on Product Hunt and relevant subreddits, and grows it to enough monthly recurring revenue to cover rent while keeping a day job.
- Building in public: a founder posts a weekly thread with signups, MRR, churn and what they shipped, including failures. The audience gives feedback, becomes early customers and spreads the word.
- A micro-SaaS stack many indie hackers use: a framework like Next.js or Laravel, managed hosting such as Vercel or a small VPS, a hosted Postgres database, Stripe or a merchant-of-record provider for payments and tax, transactional email from a service like Resend or Postmark, and simple privacy-friendly analytics.
- Validation before code: posting a landing page with a pricing table and a 'Join the waitlist' form, then reaching out to 50 potential customers directly. Only after 100 signups and several people asking to pay does the founder start building.
- A portfolio approach: an indie hacker runs several small products, such as a Chrome extension, a template marketplace and a newsletter, so no single product's revenue swing threatens their income.
Common Mistakes
- Building for months before talking to a single potential customer, then discovering nobody needs the product.
- Spending all the time on code and none on distribution, assuming a good product will market itself.
- Choosing a broad, crowded market instead of a specific niche where a solo founder can stand out.
- Pricing too low or offering only a free plan, which makes it hard to reach sustainable revenue.
- Over-engineering infrastructure for scale that may never come instead of shipping and learning.
- Depending entirely on one platform, marketplace or API whose policy or pricing change can wipe out the business overnight.
- Ignoring legal and tax basics such as sales tax and VAT on digital products, terms of service and employment contract restrictions.