PRPOSby PhoneRepair.aiJoin the waitlist

A free POS for repair shops.

PRPOS brings repair tickets, inventory and checkout together. Help shape its roadmap and build the integrations your shop needs. The POS and hosting stay free forever.

Join the waitlist

Community pilots & testers: .Public release: .

iPhone 13 with a cracked screen.

Work order

T-0042

Checked In
Device
iPhone 13 Midnight, 128 GB
Problem
Cracked screen
Condition
Crack at top right. Powers on, touch works.

Signed at drop-off

T-0042Dropped off 10:42 AM

One repair, from drop-off to paid.

Follow an iPhone 13 from drop-off to paid pickup. Its ticket, parts and sale stay connected throughout the job.

  1. Checked In

    The condition and drop-off signature stay with the ticket.

  2. Diagnosed

    The fault is confirmed. Add the screen and the labor to the estimate.

  3. In Progress

    The screen is held for this ticket, so the shelf count stays right.

  4. Ready

    Fitted, tested and ready for pickup. The balance stays with the ticket.

  5. Completed

    Payment completes the sale and updates stock. The repair and receipt stay linked.

Work order

T-0042

Completed
Device
iPhone 13 Midnight, 128 GB
Problem
Cracked screen

Intake

Condition
Crack at top right. Powers on, touch works.

Checked in 10:42 AM. Passcode saved.

Signed at drop-off

Estimate

iPhone 13 screen Part$29.00
Screen replacement Labor$100.00
Estimate before tax$129.00

Parts

iPhone 13 screen SCR-IP13

Held
On hand
4
Held
1
Available
3

Bench

Screen fitted and tested. Display and touch checked.

Part and labor$129.00
Tax 8.25%$10.64
Due at pickup$139.64

Receipt

iPhone 13 screen$29.00
Screen replacement$100.00
Tax 8.25%$10.64
Total$139.64
Cash$140.00
Change$0.36

StockScreen sold · 3 left

T-0042Dropped off 10:42 AMEstimate $129.00 plus taxOn the benchReady for pickupPaid $139.64

Why build it together?

Repair techs share fixes all the time. A POS should be built the same way.

We think AI tools have put building software within reach of the people who know the work. With their help, a shop with a clear need can turn it into a working feature. Your experience at the counter helps decide what’s worth building.

A feature built for one shop can be useful to others. Accepted improvements become part of the shared core, where other shops can help improve and maintain them. We think that shared effort is the stronger long-term choice for our industry.

We started building our own POS in 2024 because the existing systems didn’t fit the way we worked. In 2026, we separated the core and rebuilt it on TanStack, PostgreSQL and Cloudflare Hyperdrive so other shops could extend it.

Build it for your shop.

Bring an idea, a fix or an integration.

Built-in reporting keeps shop feedback close to the work. Review the capture before you send it.

Contribute a change.

Want a different payment processor? Build the integration. Point your AI agent at the GitHub repository, open a pull request and help improve PRPOS for everyone.

Share what your shop needs.

You don’t need to write code to take part. Report a problem privately through the POS, or discuss a change in a GitHub issue. Tell us what would make your day easier.

What we check before release.

Before a change reaches hosted shops, we review the code and test the workflows it affects. For a refund, that means checking the amount returned, what happened to the part, and whether the register report agrees.

We plan frequent updates, with shop feedback helping set priorities. Each change still gets reviewed and tested. If you self-host, you choose when to update.

What we’re building next.

These are the current priorities, with room for the integrations and workflows your shop needs. Feedback and contributions from shops will shape what moves up.

Pilot preparation

The everyday basics for the first pilot shops.

  • Repair tickets and work orders

    Check a device in, follow it across the bench and print the work order.

  • Inventory and receiving

    Receive parts, hold one for a repair and keep the shelf count right.

  • Checkout, refunds and the register

    Cash, manual card payments and refunds, with Helcim integration built in.

Up next

Next in line once the basics hold up.

  • Built-in AI assistant

    An assistant that works across your tickets, stock and customers, with your own model key if you prefer.

  • MCP for your own agent

    Let the AI agent you already use work with your shop’s tickets and stock.

  • Calls and texts through Quo

    Text customers and keep their calls and messages next to the repair.

Planned

Proposed so far. The order is open.

  • Customer loyalty

    Give repeat customers a reason to come back.

  • Field service

    Plan and manage repair jobs away from the counter.

  • Our phone service and AI answering

    A shop line with AI answering for calls you can’t take, on your own model key if you prefer.

  • More processors and vendors

    Community-built connections to the card processor and suppliers your shop already uses.

Missing something your shop needs? Every shop can suggest what comes next.

What’s the catch?

The core POS and hosting are free forever.

How do you make money?

We’ll make money when shops choose our partner vendors, such as a payment processor. Optional GitHub Sponsors donations will also support the work.

Can anything cost extra?

Optional managed services, such as AI usage provided by us, may have charges to cover their running costs. You can always use your own model key and pay your AI provider directly. The POS and hosting stay free either way.

You don’t need to use a partner or donate to get PRPOS or free hosting. Use the providers you prefer, build your own integrations, or self-host the whole POS.

PRPOS

Core POS and hosting

POS software$0.00
Our hosting$0.00

Core total$0.00

Optional managed services are separate. Third-party fees depend on the processor, phone or AI services you choose. If you self-host, you cover your server.

What stays your choice
Card paymentsHelcim is built in, with more merchant processors planned. Keep your existing terminal and record payments, or help build another processor integration.
SuppliersBuy parts from any supplier. Using a partner vendor is always optional.
Your dataWith our hosting, you’ll be able to export your shop’s data in PostgreSQL format and move it to your own PRPOS installation whenever you choose.
AI usageYou can always use your own model key and pay your AI provider directly. If you choose managed AI, we may charge for usage to cover our costs.
The codeRead the source, change it and run PRPOS yourself under the AGPL-3.0 license.

What does community support mean?

Discord will be our community support hub: a place to ask questions, share fixes and help other shops. You can also report bugs through the POS or GitHub. We won’t have a dedicated support desk or guaranteed response times.

We’re piloting PRPOS in one of our own shops before moving the other locations over. We depend on it at a real counter, so keeping it working and fixing bugs matters to our day, too.

Help shape PRPOS.

Tell us what your shop needs. Join as a tester, run a small pilot, or follow along until you’re ready.

Pilot shops & early testers
General public
Keep me posted
Hear when the community edition is ready to try.
Early tester
Test everyday shop workflows and tell us what needs work.
Pilot shop
Try PRPOS at your counter alongside your current system.
How do you want to take part?
How would you run it?

We’ll email you about PRPOS and early access.