Skip to content
SaaSFarersOpen Source · Open Journey
Open SourceOpen Journey

We build SaaS products. And the people who build them.

SaaSFarers is a product studio and an academy. We ship micro to enterprise SaaS, AI products and ERP systems for companies that need software which actually works, and we train the engineers the industry is short of.

Project-firstEvery cohort ships real, working software
Live projectsInterns write code that reaches production
Open by defaultShared repos, no vendor lock-in
saasfarers / what-we-do
  1. We build our own SaaS productsWe are product people firstlive
  2. We build SaaS for other companiesFrom a first version that has to reach the market this quarter, to a platform replacing fifteen years of spreadsheetsopen
  3. We build AI productsNot demosnew
  4. We train the next engineersSaaSFarers Academy is hands-on by designnow
heading · production open journey

Tools we work with: Python, Node.js, TypeScript, React, Next.js, PostgreSQL, Redis, Docker, Kubernetes, Terraform, Stripe, Razorpay, AWS, GCP, Hetzner, Frappe, Grafana, Sentry, GitHub Actions, FastAPI, LangChain, LlamaIndex, pgvector, Qdrant, OpenAI, Anthropic, Open-weight models, vLLM, Ollama, Langfuse, Ragas, ERPNext, Frappe Framework, MariaDB, Nginx, REST and webhook integrations, HTML, CSS, Astro, Static generation, WordPress (headless), Cloudflare, Netlify, Ansible, Prometheus, Loki, Process mapping, Time and motion observation, Stakeholder interviews, Data profiling, Fit-gap analysis, Cost modelling, Frappe Bench, Odoo Community, Odoo Enterprise, OWL, XML views, Odoo Studio, REST and XML-RPC integrations, Zoho One, Zoho Books, Zoho CRM, Zoho Inventory, Zoho Desk, Zoho People, Zoho Creator, Zoho Analytics, Zoho Flow, Deluge, REST APIs, Webhooks.

Our promise

Open Source. Open Journey.

Two commitments, and they are not marketing.

Open Source means we build on open technology wherever it is genuinely the right tool. You own your data, your schema and your exit. No licence cliff, no ransom at renewal, no feature you cannot inspect.

Open Journey means the way we work is visible. Shared repositories from week one. A backlog you can read. Decisions written down with their trade-offs. Estimates that change out loud instead of quietly.

You keep the keys

Repositories, infrastructure and domains are in your accounts, not ours. If you walk away tomorrow, everything keeps running.

You can read the plan

Roadmap, backlog and architecture decision records are shared, not summarised in a monthly deck.

You get the bad news early

When something slips or an approach turns out wrong, you hear it in the same week we do.

How we build

We come to you first. Then we write code.

5 stages. Something usable at the end of each one.

  1. Stage 01

    Understand

    We visit your place of work, follow a real order or case end to end, and write down where the time and the errors go.

  2. Stage 02

    Frame

    We agree what success looks like in numbers, and what we are explicitly not building in version one.

  3. Stage 03

    Design

    Data model, tenancy, integrations and the handful of architecture decisions that are expensive to reverse later.

  4. Stage 04

    Build in the open

    Two-week increments on a shared board, with something usable to click on at the end of each one.

  5. Stage 05

    Run it

    Monitoring, backups tested by restoring them, on-call, and a support line that reaches an engineer.

SaaSFarers Academy

Learn by building things that ship

The industry does not have a shortage of people who finished a course. It has a shortage of people who can take an ambiguous problem and turn it into working, maintained software. That is the gap the Academy exists to close.

01

Build, not watch

Every module ends in something deployed to a real URL, reviewed line by line by a working engineer.

02

Intern on live work

Contribute to real client projects with scoped ownership, code review and a written reference at the end.

03

Get interview-ready

Mock interviews, system design practice, and a portfolio you can defend because you actually made the decisions.

04

Get hired

We hire our strongest learners into SaaSFarers, and introduce others to the companies we work with.

From the blog

Things we have learned, written down

IndustryIndustry

ERPNext vs Odoo vs Zoho: Which Fits Your Business?

A neutral ERPNext vs Odoo vs Zoho comparison covering licensing, cost shape over five years, customisation ceilings, and GST/e-invoicing compliance.

19 Aug 20269 min read
IndustryIndustry

The Rise of the Product Engineer: Beyond Writing Code

Product engineers scope, ship, and measure their own work instead of just closing tickets. Here's what the role actually requires and how to grow into it.

29 Jul 20269 min read
AcademyAcademy & Careers

Portfolio Projects That Actually Get You Hired

Todo apps and clones don't get interviews. Here are 8 portfolio project ideas with real hard parts, plus how to write a README that gets you hired.

22 Jul 202610 min read
Questions

Straight answers about how we work

The things people ask us before the first call.

SaaSFarers is a product studio and a training academy. We build our own SaaS products, we design and build SaaS, AI and ERP products for other companies, and we run those products with ongoing technical support. Alongside that, SaaSFarers Academy trains developers through project-based courses, live-project internships, and direct hiring into our own team.

Tell us what you are trying to build.

A product idea, a process drowning in spreadsheets, an AI feature your team cannot get past the demo stage, or a career you want to change. First conversation costs nothing and usually saves something.