Open Source POS

Self-hosted point of sale, honestly reviewed. No marketing fluff, just what you get when you run it on your own hardware.

TL;DR

• What it is: A web-based point of sale application written in PHP (CodeIgniter 4), backed by MySQL/MariaDB, with a Bootstrap-based UI you deploy on your own server [GitHub README].
• Who it’s for: Small retail shop owners, restaurant operators, and inventory-heavy businesses who are tired of paying $80–$150/month for cloud POS platforms and want full control over their data [1][2].
• Cost savings: Cloud POS platforms like Lightspeed or Shopify POS run $79–$149/month. Self-hosting Open Source POS on a $6–10/month VPS eliminates that recurring cost entirely, with no per-transaction fees on top [3].
• Key strength: Surprisingly complete feature set — gift cards, restaurant tables, rewards, barcode generation, multi-tier taxation, SMS messaging, MailChimp integration, and GDPR compliance all ship in the base install [GitHub README].
• Key weakness: The project is PHP/CodeIgniter-based with a Bootstrap 3 interface — functional but dated. No mobile app. Hardware support (receipt printers, barcode scanners, cash drawers) requires careful selection from a supported hardware list. Setup assumes comfort with a LAMP stack or Docker [GitHub README].

---

What is Open Source POS

Open Source POS is a web-based point of sale system. The application runs in a browser — meaning you access it from any device on your local network, or from anywhere if you expose it via a domain — and stores all data in a MySQL or MariaDB database you control [GitHub README].

The project has been around long enough to have gone through a complete overhaul: version 3.4 dropped CodeIgniter 3 and Bootstrap 3, upgraded to CodeIgniter 4, and added security and functionality improvements. As of this review, the GitHub repository sits at 4,087 stars with a live demo at demo.opensourcepos.org where you can log in with admin / pointofsale and poke around before committing to anything [GitHub README].

What it’s not: it’s not a hosted SaaS you subscribe to, it’s not a mobile-first system with a slick app, and it’s not a full e-commerce platform. It’s a POS — designed for brick-and-mortar retail and restaurants that need to ring up sales, manage inventory, print receipts, and run reports, without writing a check to Square, Lightspeed, or Shopify every month [1][2].

The license situation is ambiguous — the merged profile returns “NOASSERTION” for the license field, which typically means automated detection couldn’t cleanly identify it. The project does ship a license file; prospective users should check opensourcepos/opensourcepos directly before any commercial deployment.

---

Why people choose it

The case for self-hosted open source POS over proprietary cloud alternatives comes down to three things that keep appearing across reviews of the category [1][2][3]:

No per-transaction or subscription fees. Cloud POS platforms have two ways to charge you: monthly software fees and transaction fees on top. Square takes 2.6% + 10¢ per in-person transaction. Shopify POS runs $79/month at its retail tier before hardware. Lightspeed charges $89–$149/month depending on plan. Open Source POS charges nothing for the software — your costs are the VPS and your own payment processor integration [3].

No vendor lock-in. Your sales history, customer database, inventory records, and supplier data live in a MySQL database you own. There’s no export-and-pray when a cloud provider changes pricing, gets acquired, or shuts down a tier. The source code is public, so if the project ever stops moving, you can fork it and maintain it yourself [1][2].

Customization without restrictions. The PHP codebase is modifiable. Businesses with specific workflows — custom tax rules, specialized receipt formats, regional payment methods — can adapt the software directly instead of waiting on a vendor roadmap or paying for a “custom integration” [1][2].

The honest version of this pitch: these advantages are real, but they come with a corresponding transfer of responsibility. When Square breaks, Square fixes it. When your self-hosted POS breaks during a Friday night dinner rush, you fix it — or you’re refunding customers [2].

One concrete comparison from the alternatives landscape: Lightspeed at $89/month is $1,068/year. Over three years, that’s $3,204 in software fees alone, before hardware or transaction costs [3]. A $10/month VPS running Open Source POS is $360 over three years. That gap funds a lot of setup time.

---

Features

Based on the GitHub README, the feature set is more complete than the “simple but intuitive” self-description suggests:

Sales and transactions:

• Sale register with full transaction logging [GitHub README]
• Quotation and invoicing [GitHub README]
• Gift cards and rewards programs [GitHub README]
• Cash up function (end-of-day reconciliation) [GitHub README]
• Printing and emailing of receipts, invoices, and quotations [GitHub README]
• Multiple payment type support (cash, card, mixed) [GitHub README]

Inventory:

• Stock management for items and kits with extensible attribute lists [GitHub README]
• Barcode generation and printing [GitHub README]
• Receivings (purchase order intake) [GitHub README]
• Customer and supplier database [GitHub README]

Taxation:

• VAT, GST, customer-specific, and multi-tier taxation rules [GitHub README]

Reporting:

• Sales, orders, expenses, inventory status reports [GitHub README]

Restaurant-specific:

• Table management [GitHub README]

Operations:

• Expenses logging [GitHub README]
• Multiuser access with permission control [GitHub README]
• SMS messaging [GitHub README]

Integrations and compliance:

• MailChimp integration [GitHub README]
• REST API [GitHub README, merged profile]
• Docker deployment [merged profile]
• GDPR-ready [GitHub README]
• Google reCAPTCHA on the login page [GitHub README]
• Multilanguage support via Weblate (community-translated) [GitHub README]
• Selectable Bootswatch themes [GitHub README]

What’s notably absent: There is no native mobile app. No built-in payment processor integration — you’ll need to wire up a card terminal separately or use a payment gateway that supports browser-based flows. No cloud sync between locations out of the box.

---

Pricing: SaaS vs self-hosted math

Open Source POS (self-hosted):

• Software: $0
• VPS (Hetzner CX22 or equivalent): ~$6–10/month
• Domain + SSL: ~$10–15/year
• Your time: 2–8 hours initial setup depending on familiarity with Docker or LAMP

Cloud POS alternatives for comparison [3]:

• Square POS: free software + 2.6% + 10¢ per in-person transaction
• Shopify POS: $79/month (Retail plan)
• Lightspeed: $89–$149/month
• Loyverse POS: free tier exists, employee management add-on $5/employee/month
• Unicenta (another open source option): $78/year for support license

Concrete math for a small retail shop processing $15,000/month:

On Square: 2.6% on $15K = $390/month in transaction fees alone — before any monthly software fee.

On Shopify POS Retail ($79/month): $79 fixed + Shopify’s own transaction fees if you use third-party payments.

On Open Source POS + Stripe terminal: Stripe’s in-person rate is 2.7% + 5¢ (with their hardware), but you’re paying no platform fee on top. At $15K/month, that’s $405/month to Stripe — same as Square. The difference is you pay nothing for the software layer, and you own your data.

The self-hosted POS play makes the most financial sense for shops with lower transaction volume or fixed monthly revenue where you want to eliminate the software subscription cost entirely. For high-volume retail, payment processing fees dominate regardless of which platform you pick [1][2].

Over 36 months, Lightspeed at $89/month = $3,204 in software fees. Open Source POS on a $8/month VPS = $288. The gap is real.

---

Deployment reality check

The README is explicit: there are multiple supported installation paths, and the project actively discourages bug reports from unsupported configurations. Supported paths are Docker Compose and direct LAMP stack installation as described in INSTALL.md [GitHub README].

What you actually need:

• A Linux server with at least 2GB RAM (Docker Compose deployment bundles PHP, MySQL, and the app together)
• Docker and docker-compose, or a manually configured Apache/Nginx + PHP + MySQL stack
• A domain name and reverse proxy if you want HTTPS and remote access
• SMTP credentials for receipt and invoice emailing
• Compatible hardware if you need physical peripherals

Hardware note: The project maintains a supported hardware datasheet on its wiki covering receipt printers, barcode scanners, and cash drawers. Not all hardware is compatible — this is worth reading before you buy any equipment [GitHub README].

What can go sideways:

The Bootstrap 3 UI is functional but won’t win design awards. If your staff has been trained on modern cloud POS interfaces, expect an adjustment period.

The project’s GitHub issues and Gitter chat are the primary support channels — there is no vendor to call when something breaks in production. The community is active enough to maintain the project (CI/CD via Travis is wired up and the live demo regenerates on new commits), but you’re ultimately responsible [GitHub README].

Payment processing is not bundled. You integrate your own card terminal. This is flexibility, but it also means configuration work that a cloud POS handles for you.

Translation is community-driven via Weblate. If your primary language isn’t English, quality varies — the project encourages contributors to maintain their own language packs [GitHub README].

Realistic setup time: 1–2 hours for a developer comfortable with Docker. 4–8 hours for someone following a step-by-step guide on a fresh VPS. For a business owner with no server experience: budget a full day or hire someone to do the initial deployment.

---

Pros and cons

Pros

• No licensing costs. The software is free. Your only recurring cost is infrastructure [1][2].
• Full data ownership. Customer records, inventory, sales history — all in a MySQL database you control. No terms-of-service changes, no export limitations [1][2].
• Genuinely complete feature set. Gift cards, rewards, restaurant tables, multi-tier taxation, SMS, barcode generation, GDPR compliance — this is not a toy [GitHub README].
• REST API included. The merged profile confirms REST API support, which means you can integrate with other systems [merged profile].
• Docker deployment. The canonical install path is Docker Compose, which is straightforward if you know Docker [GitHub README].
• Live demo. You can fully test the system before deploying anything. demo.opensourcepos.org, credentials admin / pointofsale [GitHub README].
• Active maintenance. CI is wired up, there’s a dev server for testing pre-merge commits, and the project community includes translators via Weblate [GitHub README].
• Multilanguage. Community-translated into multiple languages [GitHub README].

Cons

• PHP/Bootstrap 3 stack. This is a functional but dated aesthetic and tech choice. If you care about your staff enjoying the UI, budget time for adjustment [GitHub README].
• No mobile app. Browser-only. Fine on a tablet, but not purpose-built for mobile [GitHub README].
• No bundled payment processing. You wire up your own card terminal. Adds setup complexity compared to cloud POS platforms that ship hardware [GitHub README].
• Hardware compatibility is a real constraint. Not all receipt printers, barcode scanners, or cash drawers work. You must check the supported hardware list before purchasing [GitHub README].
• Community support only. No vendor SLA. Gitter chat and GitHub issues are your support channels [GitHub README].
• Ambiguous license. The license field in the metadata returns “NOASSERTION.” For commercial deployments, verify the actual license before proceeding.
• No cloud sync between locations out of the box. Multi-location setups require custom work or a shared database architecture.
• Limited third-party reviews specific to this project. Most available review content covers the open source POS category generically rather than opensourcepos.org specifically, making it harder to find community consensus on reliability at production scale [1][2][3].

---

Who should use this / who shouldn’t

Use Open Source POS if:

• You run a small retail shop, café, or restaurant and are paying $79–$149/month for a cloud POS — the math closes within weeks.
• You have someone technical (or are willing to learn Docker) who can handle the initial deployment.
• You need to store sensitive customer data and don’t want it on a third party’s servers.
• You have region-specific tax rules or receipt requirements that cloud platforms don’t support cleanly.
• You need restaurant table management without paying for a hospitality-specific POS add-on.

Skip it (use Loyverse free tier) if:

• You want something functional without any server setup — Loyverse’s free tier covers basic retail POS without a monthly fee and runs on a tablet immediately [3].

Skip it (use Square) if:

• You’re a new business with low volume and want zero setup time. Square’s free tier and free hardware promotion will get you selling in an afternoon with no technical overhead.

Skip it (use Lightspeed) if:

• You’re running a multi-location retail operation that needs vendor-backed support, deep inventory analytics, and integrated e-commerce syncing.

Skip it entirely if:

• You have no technical person available and no budget to hire one for setup. A self-hosted POS that breaks at 8pm on a Saturday is worse than a cloud POS with a $99/month support line.

---

Alternatives worth considering

From the softwaresuggest.com roundup and the broader open source POS category [3]:

• Unicenta — another PHP-based open source POS, more mature UI than opensourcepos in some respects. Annual support license available at ~$78/year for those who want a paid support option [3].
• Floreant POS — Java-based, specifically designed for restaurants with table management focus. Good choice if food service is the primary use case [3].
• Odoo — open source ERP with POS module included. Overkill if you just need a POS, but if you already need CRM, accounting, and inventory, the POS comes along for the ride. Enterprise version at $20/user/month [3].
• WallacePOS — free and open source, mentioned in the same roundup but with less documentation and community activity [3].
• Loyverse POS — freemium, not fully open source, but has a genuinely usable free tier for small retail. Worth comparing before committing to a self-hosted stack [3].
• Square POS — the benchmark closed-source comparison. Zero monthly software fee, no server to run, but you’re inside Square’s ecosystem forever.

For a non-technical founder specifically, the honest shortlist is Open Source POS vs Loyverse free tier vs Square free tier. If you can handle Docker: Open Source POS wins on cost and data ownership. If you can’t: Loyverse or Square will serve you until you can.

---

Bottom line

Open Source POS does what it says: it’s a solid, complete, self-hosted point of sale with features that match or exceed mid-market cloud POS platforms in the $80–$150/month range. The PHP/Bootstrap stack won’t win a design competition in 2026, and you’ll need technical hands for setup and maintenance. But for a small retail or restaurant operator who understands that a $6/month VPS replaces a $100+/month SaaS subscription and returns full ownership of their business data, the trade-off is obvious.

The live demo at demo.opensourcepos.org removes the guesswork — spend 20 minutes in it before making any decision. If the interface works for your workflow, the setup cost is a one-time investment. If the interface feels wrong, no amount of cost savings will make your staff use it reliably.

If the setup is the blocker, that’s exactly what upready.dev handles for clients. One-time deployment, your infrastructure, your data.

---

Sources

1. osssoftware.org — “Open Source POS Software Explained” (January 15, 2024). https://osssoftware.org/blog/open-source-pos-software-explained/
2. osssoftware.org — “Open Source POS System Features” (January 14, 2024). https://osssoftware.org/blog/open-source-pos-system-features/
3. softwaresuggest.com — “14 Best Free Open Source POS Software in 2026 (Top Picks)” (Updated March 10, 2026). https://www.softwaresuggest.com/blog/free-open-source-pos-software/

Primary sources:

• GitHub repository and README: https://github.com/opensourcepos/opensourcepos (4,087 stars)
• Live demo: https://demo.opensourcepos.org
• Development demo: https://dev.opensourcepos.org
• Community translation: https://translate.opensourcepos.org