r/SideProject Dec 18 '25

As the year wraps up: what’s the project you’re most proud of building and why?

Upvotes

Like the title says, instead of what you built or how much money it made, I’m curious what project you’re most proud of this year and why.

Could be a client site, a personal project, something that never launched, or something that made £0.

Any lessons learned?

Would love to read a few reflections as the year wraps up.


r/SideProject Oct 19 '25

Share your ***Not-AI*** projects

Upvotes

I miss seeing original ideas that aren’t just another AI wrapper.

If you’re building something in 2025 that’s not AI-related here’s your space to self-promote.

Drop your project here


r/SideProject 19h ago

I spent 1,000+ hours building an interactive 3D reconstruction of Ancient Egypt for the web. Entire scenes are ~1–2MB, no ads, no logins.

Enable HLS to view with audio, or disable this notification

Upvotes

Hey everyone,

A few months ago I shared the early concept of Expeditione here. Today, I wanted to share a closer look at the flagship expedition : Ancient Egypt.

Most educational content online is choked with cookie popups, ad banners, and auto-generated slop. I wanted to build the exact opposite : an authentic, ad-free digital museum you can explore straight from your browser with zero friction.

What’s inside the expedition :

  • 5 Handcrafted Dioramas : Everyday homes, Nile farming, limestone quarries, temples, and the Giza Plateau.
  • Interactive Tools : Dynamic scanner inspections, archaeological cutaways, and a 1:1 "True Size" mode at the Pyramids where you can stack structures up to 150m for real-world scale.
  • Everyday Life Focus : Rather than just monuments, it covers how ordinary Egyptians lived, worked, and built.
  • Classroom Resources : Downloadable educator guides and student worksheets with no sign-ups or email gates.

The Performance & Optimization Pipeline:

Getting interactive 3D to run butter-smooth on 6-year-old Chromebooks and budget mobile devices meant being ruthless with asset weight :

  • Payloads: Initial core load is ~2MB, with subsequent scenes averaging ~1MB each (Pyramids sits around 2–3MB due to scale).
  • Stack: Three.js, Blender, and GSAP for animation sequencing.

It’s completely free—no tracking, no ads, no paywalls.

Explore it here : https://expeditione.fun/expeditions/ancient-egypt/

Would be really glad to hear your thoughts on how you feel!

I hope you enjoy the expedition 💖


r/SideProject 6h ago

Got my first GitHub star today 🎉

Upvotes

It’s only one star, but it’s my first one, and seeing someone I don’t know star something I made genuinely makes me happy lol


r/SideProject 19h ago

Let Me Googly Eye That For You

Enable HLS to view with audio, or disable this notification

Upvotes

Realized 99% of my ideas are ass and I'm better off working a normal job and leaving the entrepreneur thing to you all. Still have a few days left before my Claude sub lapses, so I made an extension that, like its creator, has no utility. Kids love it though and it's good for a laugh when I forget I've got the stupid thing on, especially on news sites, so no ragrets.

Anywho. Good luck to everyone building in here, been a lot of fun seeing the cool stuff you all come up with. Hope every one of you become zillionaires, if you ever need a beta tester or a pair of bad eyes to review your work, give me a shout.


r/SideProject 12h ago

The annoying part of making more money is the expenses get bigger too

Upvotes

My side project has finally gotten to the point where the monthly numbers actually feel meaningful, which is great but I wasn’t expecting the timing of expenses to become such a headache. Early on everything was tiny. Now I’ll have a really good month and then a bunch of expenses seem to land together before all the money from that month has actually cleared. I’m starting to pay more attention to when money moves instead of just whether the month was profitable overall.

For anyone whose side project grew into something substantial, did you change how you handled expenses as it got bigger or just start keeping a larger cash buffer around?


r/SideProject 2h ago

Two people can have exactly what the other wants to learn and still never meet each others online.

Enable HLS to view with audio, or disable this notification

Upvotes

I've been thinking about this for a while.

There are millions of people online who know things we want to learn.

Someone knows Figma.

Someone knows how to code.

Someone knows video editing, marketing, photography, writing, a language, or almost anything else.

The knowledge is already out there.

But finding the right person to actually learn from can be surprisingly random.

You can search through Reddit communities, Discord servers, Instagram, LinkedIn, and other places.

You might eventually find someone who knows the skill.

But then there's another question: are they actually interested in teaching or exchanging knowledge with someone?

That's where the idea for my project came from.

I built a platform called Agora around a simple idea:

What if people could find each other based on what they want to learn and what they can teach?

For example:

* You know coding and want to learn UI/UX.

* Someone else knows UI/UX and wants to learn coding.

That would be a strong match because both people have something the other person wants.

With Agora, you create a profile, add the skills you can teach and the ones you want to learn, and then explore potential matches.

You can also filter people based on skills and location.

If you find someone you're interested in learning from, you send a connection request. Messaging only opens after the other person accepts it.

I kept that flow intentionally because I didn't want the platform to become another place where people could message hundreds of strangers.

The project is still an MVP. Agora


r/SideProject 16m ago

A 3-year contract may not mean 3 years of certainty

Upvotes

The length of a contract can create a false sense of certainty. A fintech founder can sign a three-year agreement with a banking partner, payment provider, or infrastructure company and reasonably assume that they now have three years of predictable commercial terms, but that assumption only holds if the economics of the relationship are actually stable for those three years.

I’ve come across agreements where the headline term is three years, but either party has a right to review or renegotiate pricing every few months. On paper, the relationship continues for three years, yet in practice, the parties are effectively reopening part of the commercial deal several times a year.

That distinction matters more than it might initially appear.

## A Long Contract Does Not Always Mean Long-Term Certainty

Consider what happens when a fintech spends months negotiating pricing with a critical partner, signs the agreement, completes the technical integration, and then builds its own operations around those economics.

The business may set its customer pricing based on those costs, enter into contracts with its own customers, hire employees, invest in infrastructure, and make growth decisions based on the assumption that the underlying commercial arrangement will remain reasonably predictable.

If the same agreement then allows the partner to revisit transaction fees, minimum commitments, or other important commercial terms every quarter, some of that certainty disappears.

The contract may still have three years left to run, but the business is repeatedly being asked to consider whether the economics that support its model might change.

That is not necessarily a problem with the duration of the agreement. It is a problem with what the duration actually protects.

## Review Rights Are Not Necessarily a Bad Thing

I do not think commercial review mechanisms are inherently problematic, particularly in fintech, where the economics of a relationship can genuinely change over time.

Transaction volumes may increase significantly, the scope of services may expand, regulatory requirements may introduce additional costs, or infrastructure expenses may change in ways that neither party could reasonably have predicted when the agreement was signed. Over a three-year relationship, the product and the business itself may also evolve considerably.

A contract should have enough flexibility to deal with genuine changes like these.

The issue arises when one party receives a broad right to reopen the commercial arrangement simply because a certain period of time has passed.

The fact that another quarter has ended does not, by itself, tell you whether the economics of the relationship have materially changed.

A more useful approach is to identify the events that should actually trigger a review. The parties might agree that pricing can be reconsidered if transaction volumes move substantially beyond an agreed threshold, if the scope of services changes materially, if a new regulatory requirement creates significant additional costs, or if a defined external cost increases beyond an agreed level.

Those are identifiable commercial events that both parties can understand.

"Another quarter has passed" is a much weaker basis for reopening a deal.

The distinction is important because a review mechanism should ideally respond to a genuine change in the relationship rather than become a routine opportunity to renegotiate terms.

## The Real Problem Is Often What Happens After the Review

There is another part of these provisions that deserves just as much attention as the trigger itself: what happens once the review actually begins?

A clause might say that the parties will review pricing every quarter, but that does not tell you what happens when they cannot agree on a new price.

Does the existing pricing continue until an agreement is reached? Can either party terminate the relationship? Is there a temporary pricing mechanism? Does the disagreement move through an escalation process? How much notice must be given before a proposed change takes effect?

Those details can completely change the commercial impact of the provision.

I tend to look at a review mechanism as a small negotiation process built into the larger agreement. You need to understand what triggers the process, what can actually be changed, how often the review can occur, what evidence supports the proposed adjustment, how much notice is required, and what happens if the parties reach an impasse.

The scope of the review is particularly important.

If an agreement allows a quarterly review of "commercial terms," that could potentially give the parties a much broader opportunity to revisit the relationship than a provision allowing them to reconsider one specific transaction fee after transaction volumes cross a defined threshold.

Those two provisions may sound similar during negotiations, but they can have very different consequences once the business has scaled.

## Changes Upstream Can Affect the Entire Business

This becomes especially important when the partner sits underneath your own customer relationships.

Suppose a banking or payments partner changes its pricing after you have already priced your product and signed customer contracts based on the original economics. Your customers may not care that your upstream provider changed its fees or that the contract allowed the change.

You still have to operate the product, pay your employees, maintain infrastructure, provide support, and deliver whatever you promised your own customers.

A change in one upstream agreement can therefore move through the entire business.

This is why I think founders should pay particular attention to pricing review mechanisms when negotiating relationships with critical fintech infrastructure providers. The question is not simply whether the provider can change its pricing, but whether your business has enough predictability to absorb that change without having to immediately revisit everything downstream.

## What Does "Three Years" Actually Protect?

This has changed the way I look at long-term fintech agreements.

When I see a three-year agreement, I do not think the most important question is simply, "How long does this contract last?"

The more useful question is, "How long are the commercial terms actually protected?"

Those are very different questions.

A three-year agreement with broad quarterly renegotiation rights may give you three years of contractual duration while providing considerably less commercial certainty than the headline term suggests.

That does not automatically make the agreement bad. There may be perfectly legitimate reasons for including a review mechanism, and in some relationships, some degree of flexibility is necessary.

But if the economics of the relationship are important to your business, the review mechanism deserves as much attention as the initial pricing.

## Build Flexibility Around Clear Triggers

Long-term agreements do not need to pretend that nothing will change.

In fact, the better agreements acknowledge that circumstances will change and establish a sensible process for dealing with those changes before either party is forced into an unexpected renegotiation.

That means defining what constitutes a material change, identifying which commercial terms can be reviewed, setting reasonable review periods, establishing notice requirements, and deciding what happens if the parties cannot reach agreement.

The objective is not to remove flexibility from the relationship.

It is to make that flexibility predictable.

When both parties know what can trigger a review and what happens afterwards, the agreement becomes much easier to manage as the business evolves.

## Conclusion

A long-term contract is only as predictable as the provisions that sit underneath its headline term.

A three-year fintech agreement can still leave a business exposed to significant commercial uncertainty if pricing, fees, minimum commitments, or other important terms can be reopened regularly without clear triggers or defined limits.

The lesson I would take from this is simple: when negotiating a long-term fintech partnership, do not only ask how long the agreement lasts. Ask how long the economics are protected, what events can change them, and what happens if the parties cannot agree.

The strongest long-term agreements do not assume that nothing will change.

They decide in advance what kind of change is significant enough to reopen the conversation, how that conversation will take place, and what happens if the conversation does not lead to an agreement.

That is what makes a long-term contract commercially useful rather than simply long.


r/SideProject 26m ago

I built a PDF scanner for iPhone that keeps your documents on the phone. No account, free to scan, sign and OCR.

Upvotes

I'm a solo developer and I've spent the last while building PDFz, a PDF scanner and editor for iPhone and iPad. Posting because I kept looking for one that doesn't send every page to someone's server, and ended up writing it.

What it does

  • Scan paper with the camera: auto-crop, straightening, shadow removal, multi-page, ID card and passport modes
  • OCR on the phone's own neural engine, so searching inside a scan works in airplane mode
  • Edit text and images on the page, reorder and rotate pages, add watermarks and page numbers
  • Sign with your finger, fill forms, tick boxes, stamp
  • Merge, split, compress (you see the new size before you save)
  • Translate a document, or point the camera at printed text
  • Convert PDF to Word, Excel and PowerPoint
  • A Wi-Fi desk: open an address on your laptop and drop PDFs onto the phone over local Wi-Fi, no cloud, nothing to install on the laptop

What stays on the phone

Everything above except one thing: Word/Excel/PowerPoint conversion runs on my server, because no phone ships with a layout engine that can rebuild a document properly. The file is deleted the moment the job finishes, the result is deleted when you download it, and nothing about the contents is logged. That's the only job that leaves the device, and it's written plainly in the privacy policy rather than buried.

No account, no sign-up. There's no database of you to leak because there isn't one.

What's free vs paid

Scanning, OCR, editing, signing, filling forms and search are free, with no account and no page limit. The free version shows ads.

Plus is $4.99/month or $29.99/year with a 7-day free trial, and there's a $1.99 week if you just need it for one document. It removes the ads and unlocks keeping the converted Office files, saving translated documents, merging more than two files, the smallest compression tier, passwords, form building, camera translation and the Wi-Fi desk. Previewing a conversion is free either way, so you can see the result before paying for anything. Those are US prices; your store may differ.

One more thing

It's in 49 languages, and Arabic isn't an afterthought: the whole app is right-to-left, and mixed Arabic/English documents keep their reading order when converted to Word. That was the reason I started building it.

App Store: https://apps.apple.com/app/id6754037398

Site: https://pdfz.ai

Happy to answer anything, including "why not just use Files or Notes". If something breaks, tell me here or at support@pdfz.ai. I read every message.


r/SideProject 12h ago

I built an app where you get paired with one stranger, trade songs for 24 hours, and then the chat deletes itself

Upvotes

My best conversations about music have never been on music apps. They've been with strangers — someone at a party, a guy in a record store, a person in a comment thread who linked me something I'd never have found on my own.

Every music app I use turns that into a numbers game. Followers, playlist counts, monthly listeners. So I spent the last several months building the opposite.

It's called MusicPool. You pick a vibe, a genre, a mood, a decade. You get anonymously paired with one person who picked the same thing. You have 24 hours to talk and trade songs. Then the chat disappears, always. If you both want to, you can unlock each other's profiles before it goes, their name, what they're into, what other people have said about their taste. But the conversation itself is gone either way.

No feed. No followers. One stranger, one day, and whatever you played each other.

I'm the only person working on it, and it launched recently enough that I'm still finding rough edges. If you try it and something is confusing or broken, tell me here, I read everything and I'd rather hear it blunt than polite.

One honest catch: it only works if there are people in the pool. It's new, so matches can take a while right now. If the idea appeals to you, sending it to one person who'd be into it does more than anything else I could do on my own, the whole thing gets better the more people are in it.

I'm in the comments all day. Ask me anything about it, or just tell me the last song you'd want to hand a stranger, I'm curious what this sub would send.


r/SideProject 16h ago

Was addicted to building houses in sims and now addicted to making the perfect floor plan for my new apartment

Enable HLS to view with audio, or disable this notification

Upvotes

Just bought a new place and got obsessed with figuring out the PERFECT floor plan, I even made a website for myself thats sims3 inspired where I can upload a floor plan and arrange it. I spent like 50 hours in a week this week lol

[https://planplan.me\](https://planplan.me) I dont want to monetize it, 100% free and will remain free if someone wants to have fun with it, enjoy


r/SideProject 10m ago

Manutenzione, scadenze e spese dell’auto: voi come tenete tutto sotto controllo?

Upvotes

Ciao a tutti! Ho sviluppato Carburo partendo da un’esigenza personale: riuscire a gestire meglio manutenzione, scadenze e spese della macchina.

Tra rifornimenti, assicurazione, bollo, revisione e lavori fatti nel tempo, tenere uno storico ordinato diventa complicato. Mi interessava poter ritrovare facilmente quando avevo fatto un intervento, a quanti chilometri e quanto avevo speso.

Per organizzare queste informazioni, secondo me sono utili tre cose:

  • Per ogni intervento: data, chilometraggio, costo e una nota su cosa è stato fatto, conservando la ricevuta.
  • Per le prossime manutenzioni: tenere insieme scadenza temporale e chilometrica, seguendo le indicazioni del costruttore.
  • Per le spese: distinguere carburante, costi ricorrenti e manutenzione, così da capire dove finiscono i soldi durante l’anno.

Voi come vi organizzate? Usate un’app, un foglio Excel oppure vi affidate ai promemoria dell’officina? Cosa trovate più difficile da tenere aggiornato?

Da questa esigenza è nata Carburo, l’app Android che ho sviluppato per raccogliere queste informazioni. Gestisce rifornimenti, consumi, spese e scadenze e permette anche di consultare i prezzi dei carburanti nelle vicinanze. È gratuita, senza pubblicità e senza account; lo storico resta sul telefono.

Per chi fosse interessato: Carburo su Google Play.


r/SideProject 8h ago

Does anyone else start a tiny side project and accidentally turn it into something much bigger?

Enable HLS to view with audio, or disable this notification

Upvotes

I originally just wanted to build a simple caffeine tracker. (Included a demo above)

But pretty quickly I realized that manually typing in the brand, flavor, caffeine amount, size, etc. every time you drink something gets annoying.

So I started building an energy drink database to make logging easier.

Then that turned into barcode scanning, drink pages, a website for the database, and now I'm thinking about what else the data could be useful for.

I always see post about people talk about how they start a small project but then they start adding feature after feature and it never gets "done."

I didn't think I would experience that until now.

Does this happen to anyone else?

Do you usually let the project keep growing when you see new possibilities, or do you force yourself to stick to the original idea?


r/SideProject 7h ago

Roast my zero-cost hustle idea: A "Ruthless" International Human Alarm Clock.

Upvotes

I realized that when it's 6 AM in the US, it's the middle of the afternoon for me here in India.

I'm thinking of starting a very simple service: I will literally spam-call busy professionals on WhatsApp until they wake up and send me a photo of them drinking a glass of water or standing outside their bed.

People easily snooze regular alarms, but they can't snooze a real, persistent human who won't hang up.

Do you guys think people would pay $10/week for this? I want to test this out on 3-4 people for FREE just to see if the model actually works before I try to build a website or anything.

Thoughts? Would love some brutal feedback!


r/SideProject 3h ago

Building an open-source coding agent that wastes less model spend

Upvotes
I'm building Felan, an open-source, model-portable coding agent built on Pi. The goal is to get software work done correctly with less model spend, rather than chase a lower token count on its own.


The harness combines model routing, progressive context, compact tool output and explicit task state. We want to reduce waste around the model without treating a cheaper failed run as a win.


Across six controlled, extension-specific comparisons, we measured 36.6% lower aggregate model cost against disabled baselines. These weren't comparisons against other coding agents or a test of all extensions enabled together. The RTK comparison also had one timeout: 5/6 candidate runs passed versus 6/6 baseline runs, so I wouldn't present the cost result as proof of equal reliability.


Felan is MIT-licensed and doesn't require a Felan account. You can run `npx @felan-ai/felan` with Node.js 22.19 or newer and a supported model-provider account or API credential. It runs with your host permissions, not inside a sandbox.


Repo: https://github.com/felan-ai/felan
Benchmarks: https://felan-ai.github.io/harness-bench/results/2026-09-felan-extensions/


Where do your current coding agents waste the most work: context, tool output, retries or something else?

r/SideProject 11h ago

I built Stackray to inspect website tech stacks/OSINT details and keep a history of the results

Enable HLS to view with audio, or disable this notification

Upvotes

Stackray is a website/url scanner that shows the technologies it detects, DNS records, subdomains, and other OSINT details.

Check it out: https://stackray.app

It's open source under MIT, and there's a one-click to deploy Railway template if you want your own instance for private scanning where you can also invite users into your instance, schedule recurring scans, track changes, and setup change alerts using resend (email alerts) and slack. Source code.

If you try your own site what does it get right or miss?


r/SideProject 3h ago

Built Analytika, a website analytics platform

Upvotes

I've been working on Analytika for a while and finally got it to a point where I wanted to share it.

It's an analytics platform focused on visitor journeys, live visitors, funnels, attribution, revenue, Search Console and social traffic.

The goal is basically to have a better picture of what people are actually doing on your website and where your conversions are coming from.

I'd really appreciate some honest feedback.

What do you think of the UI?
Does the product make sense when you first look at it?
Anything you think is missing or could be done better?

https://analytika.me

Happy to hear criticism too, that's mainly why I'm posting it here.


r/SideProject 1m ago

Been working on this little side project for a while, so figured I’d finally share it here

Upvotes

The idea itself definitely isn’t new. There are already a ton of affirmation apps out there. What I wanted to do differently was put a lot more focus on the design and the feeling of using it.

I wanted it to feel less like opening an app, reading a quote, and closing it, and more like having a small, calming moment in your day. So, I’ve been playing around with motion, visuals, interactions, and little details to make the experience feel more alive rather than just a collection of static affirmations.

It’s still a side project and I’m figuring things out as I go, so I’d genuinely love some feedback.

What do you think? Does the design/experience work for you? Anything that feels unnecessary, confusing, or could be improved?

https://soul-lift.net/

Would really appreciate any honest feedback, good or bad


r/SideProject 8m ago

I built a local-first encrypted workspace for files + notes — now I need people to tell me what’s wrong with it

Upvotes

I've been building Filarr for quite a while. (The first commit is dated June 8, 2024)

It originally started because I wanted something pretty simple:

a place for my files and notes where privacy wasn't something I had to add afterwards.

I liked the local-first philosophy of tools like Obsidian, but I also wanted my data encrypted at rest by default, file management built in, and optional sync without giving the storage provider access to the plaintext.

That slowly turned into Filarr.

Today it's a desktop workspace where you can:

  • manage files and folders
  • write and link notes
  • use graph / canvas views
  • work completely offline
  • keep the vault encrypted locally
  • optionally sync encrypted data between devices
  • use your own S3-compatible storage through BYOS

The local version doesn't require a subscription.

I'm currently on v3.1.1, and I've reached the point where adding more features is probably less useful than actually getting the product in front of people.

So I'm looking for criticism rather than compliments.

If you're into local-first software, PKM, privacy or self-hosting, I'd particularly like to know:

  1. Do you understand what Filarr is within a few seconds?
  2. What would stop you from trusting it with your files?
  3. If you already use Obsidian + Cryptomator / VeraCrypt / Syncthing / similar tools, is there actually a reason you'd switch?
  4. What, if anything, would you personally pay for?
  5. Do you find it intuitive and easy to use?
  6. What would you miss about this tool?

Website: https://filarr.com
If you don't want to download the software: https://app.filarr.com

I'll be around to answer technical questions too — encryption, sync architecture, BYOS, whatever.

Feel free to be harsh. That's genuinely more useful to me right now.

Thanks


r/SideProject 3h ago

FocusMate Adventure: I turned study timers into quests, XP and streaks. Does the game loop actually help?

Upvotes

I started building FocusMate Adventure after struggling to stay consistent with studying. I wanted focus sessions to feel less like watching a clock and more like making progress in a game.

The app turns sessions into quests and rewards consistency with XP, levels and streaks. It is free on iPhone and Android, but I am still trying to understand whether these game elements genuinely motivate people or simply make the timer look more interesting.

If you use focus or study timers, what actually makes you return to one every day? Streaks, rewards, distraction blocking, simplicity, or something else?

I would genuinely appreciate honest feedback, especially if you think the idea is unnecessary or something important is missing.


r/SideProject 7h ago

I built an Android shift-coverage demo. What would make a supervisor actually trust the workflow?

Upvotes

I’m working on a private Android side project for an employer problem: someone cannot cover a shift, and the supervisor needs a clear way to compare options and confirm coverage.

The current demo walks through an uncovered shift, candidate availability, arrival/assistance details, simulated outreach, and a coverage confirmation. It uses fictional data only—it does not contact real workers or provide a live staffing service.

I’d especially like feedback from small-business owners, supervisors, schedulers, and staffing coordinators:

  • What information would you need before choosing someone?
  • Where could a screen accidentally imply that a person has agreed when they haven’t?
  • What would make a confirmation trustworthy, or make you abandon the workflow?

I’m also recruiting adult Android volunteers for the upcoming private beta. The first usability session should take 5–10 minutes; once the Google Play closed test opens, I’m seeking people willing to stay opted in for 14 days and try it more than once. No app account or purchases are required.

Important: the Play invitation is not live yet. This is pre-launch recruitment, not an available download. I’m keeping the app name private during this stage and will share verified access privately when it opens. Testing is voluntary and unpaid; honest criticism is welcome, and I’m not asking for ratings or positive reviews.

If this matches your experience, I’d appreciate a comment about the workflow—or a DM if you want to volunteer. Please don’t post email addresses or real workplace/employee information publicly.

— Thomas


r/SideProject 4h ago

My lab found a way to migrate between embedding models with zero downtime.

Upvotes

So I've been messinga round with embedding models for a bit, and I think they are interesting enough to experiment with. They are useful for rag, especially in a localllm sense because you can ground your answers in truth.

But what happens if you have a billion documents, and you decide to upgrade your model to a "better" one? on an h100, that would take about 108 days, just to upgrade the vectors so u can start serving again (tested qwen embed 8b on h100). Even if you aren't doing 1b vectors, and are doing just 50 million, upgrading can still take a considerable time.

Me and my research lab decided to tackle this problem, and we came up with embedflow.

The method is really simple; from the old index made with the source model, take K documents and rerank them with the new model. We see that when K is sufficient, the retrieval quality is the same as target model. (determining k is the hard part). I've tested 63 migrations on upto 1 million documents.

The best result I got was upgrading qwen4b -> to 8b, and at 50 documents, it was the same as native retrieval.

This method forgos the expensive backfill that comes with upgrading, as you can directly take documents from the old index.

embedflow works with qdrant, and can be easily downloaded with pypi

pip install embedflow

the github is public: https://github.com/arnsri33/embedflow

I want you guys to try it out, and see if you guys can use it in your own workflow.


r/SideProject 21m ago

There are already a ton of SaaS boilerplates. I built one anyway — here’s what I think they’re missing

Upvotes

There are already a lot of SaaS boilerplates.

I know.

That was actually one of the reasons I hesitated before turning this into a product.

I didn’t want to make another repo whose value was basically:

“here’s auth, Stripe/Paddle, a landing page and some components.”

Coding agents can generate a lot of that now anyway.

What kept bothering me was that every time I started a real SaaS, the first few weeks still disappeared into the parts that only become annoying once everything has to work together:

  • auth and application state;
  • subscriptions and webhook reconciliation;
  • usage credits / metered economics;
  • long-running background jobs;
  • migrations;
  • account deletion and data lifecycle;
  • deployment configuration;
  • all the failure cases between those pieces.

That was especially true for the kind of products I tend to build: Python SaaS with AI, async work and usage-based economics.

So I packaged the production foundation I actually wanted to reuse.

It’s called The Fabrica.

It’s a FastAPI + Next.js codebase with:

  • Clerk auth;
  • Paddle subscriptions;
  • credit ledger / metered usage;
  • Celery + Redis background jobs;
  • Postgres + Alembic;
  • account deletion / data lifecycle;
  • email;
  • production configuration;
  • 11 locales.

But the part I think makes it useful isn’t the checklist.

1. The pieces are wired together as a system.

Billing updates account state and credits. Background work fits the same application model. Deletion has actual lifecycle semantics. The point is not having 20 isolated integrations sitting in a repo.

2. It’s aimed at production failure modes, not just getting localhost running.

Before releasing v0.1.0 I forced the buyer path and billing flow through real end-to-end checks.

A real Paddle sandbox payment exposed a concurrency bug our existing tests had missed: two different subscription events could process at the same time, both observe that no local subscription existed, and race to insert the same external ID.

A fresh-clone release pass also found schema drift, ambient environment variables hiding setup assumptions, a real CLI crash behind type errors, and config that was correct in the frontend while the backend was still using the factory default.

Those are exactly the kinds of bugs I don’t want to rediscover on product number two, three or four.

3. I wanted it to remain my foundation, not become a fork I’m scared to modify.

Product-specific code has an explicit _domain/ boundary, and the repo includes an upstream-update procedure so the idea is that you can heavily customize your product without mixing every business-specific decision into the foundation itself.

That part will only really prove itself across future releases, but it was important enough that I designed around it from the start.

4. It’s deliberately opinionated about the stack.

It isn’t trying to be the universal SaaS starter.

It’s for someone who already wants something close to:

FastAPI + Next.js + Postgres + workers + Paddle + metered usage

and would rather start building the actual product than assemble that layer again.

So the positioning I ended up with is less:

“SaaS boilerplate with lots of features”

and more:

“Everything before your first feature, already done.”

The Fabrica v0.1.0 is live now.

€349 one-time for the Solo license.

[https://www.thefabrica.dev/?utm_source=reddit&utm_medium=community&utm_campaign=fabrica_launch_010&utm_content=sideproject_launch]()

I’m still validating whether this distinction matters enough for other builders to pay for it.

So I’d actually be interested in the skeptical answer too: if you already know there are dozens of SaaS starters, what would make one worth paying for instead of assembling the stack yourself or having an agent generate it?


r/SideProject 21m ago

I made a free invoice generator that has no backend — your data physically can't leak

Thumbnail
quietinvoice.lab.karolkrakowski.pl
Upvotes

One static page: editor + live A4 preview + PDF export, everything in the browser, invoice data in localStorage only. No account, no limits, works offline. Built it because I read one privacy policy too many. Free; the only paid thing is a $12 cosmetic unlock. Feedback welcome — especially from people who invoice weekly.


r/SideProject 21m ago

Answer four questions about your idea and I'll send you a one-page brief on it

Upvotes

I'm doing ten of these by hand, then I stop.

Reply here or DM me your answers and you get back one page: who it's for, the biggest assumption, the biggest risk, and one move for this week. I'll post the brief in the thread unless you ask me not to.

  1. One sentence. What are you trying to change, and for whom?
  2. Tell me about the last time someone in that group hit the problem you're trying to solve. What did they actually do?
  3. If you had to bet on one thing being wrong about this idea, what would it be?
  4. What's the smallest move you could make this week to find out?

Why these four: they're the ones I skipped on the things I built that nobody but me wanted. I built a framework around them afterwards. That's what writes the brief.