frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Big Tech vs. OpenClaw

https://www.jakequist.com/thoughts/big-tech-vs-openclaw/
1•headalgorithm•2m ago•0 comments

Anofox Forecast

https://anofox.com/docs/forecast/
1•marklit•2m ago•0 comments

Ask HN: How do you figure out where data lives across 100 microservices?

1•doodledood•2m ago•0 comments

Motus: A Unified Latent Action World Model

https://arxiv.org/abs/2512.13030
1•mnming•2m ago•0 comments

Rotten Tomatoes Desperately Claims 'Impossible' Rating for 'Melania' Is Real

https://www.thedailybeast.com/obsessed/rotten-tomatoes-desperately-claims-impossible-rating-for-m...
1•juujian•4m ago•0 comments

The protein denitrosylase SCoR2 regulates lipogenesis and fat storage [pdf]

https://www.science.org/doi/10.1126/scisignal.adv0660
1•thunderbong•6m ago•0 comments

Los Alamos Primer

https://blog.szczepan.org/blog/los-alamos-primer/
1•alkyon•8m ago•0 comments

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
1•DEntisT_•11m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
1•tosh•11m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•11m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•14m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
4•sakanakana00•17m ago•0 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•20m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
3•Tehnix•20m ago•1 comments

Skim – vibe review your PRs

https://github.com/Haizzz/skim
2•haizzz•22m ago•1 comments

Show HN: Open-source AI assistant for interview reasoning

https://github.com/evinjohnn/natively-cluely-ai-assistant
4•Nive11•22m ago•6 comments

Tech Edge: A Living Playbook for America's Technology Long Game

https://csis-website-prod.s3.amazonaws.com/s3fs-public/2026-01/260120_EST_Tech_Edge_0.pdf?Version...
2•hunglee2•26m ago•0 comments

Golden Cross vs. Death Cross: Crypto Trading Guide

https://chartscout.io/golden-cross-vs-death-cross-crypto-trading-guide
2•chartscout•28m ago•0 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
3•AlexeyBrin•31m ago•0 comments

What the longevity experts don't tell you

https://machielreyneke.com/blog/longevity-lessons/
2•machielrey•32m ago•1 comments

Monzo wrongly denied refunds to fraud and scam victims

https://www.theguardian.com/money/2026/feb/07/monzo-natwest-hsbc-refunds-fraud-scam-fos-ombudsman
3•tablets•37m ago•1 comments

They were drawn to Korea with dreams of K-pop stardom – but then let down

https://www.bbc.com/news/articles/cvgnq9rwyqno
2•breve•39m ago•0 comments

Show HN: AI-Powered Merchant Intelligence

https://nodee.co
1•jjkirsch•42m ago•0 comments

Bash parallel tasks and error handling

https://github.com/themattrix/bash-concurrent
2•pastage•42m ago•0 comments

Let's compile Quake like it's 1997

https://fabiensanglard.net/compile_like_1997/index.html
2•billiob•43m ago•0 comments

Reverse Engineering Medium.com's Editor: How Copy, Paste, and Images Work

https://app.writtte.com/read/gP0H6W5
2•birdculture•48m ago•0 comments

Go 1.22, SQLite, and Next.js: The "Boring" Back End

https://mohammedeabdelaziz.github.io/articles/go-next-pt-2
1•mohammede•54m ago•0 comments

Laibach the Whistleblowers [video]

https://www.youtube.com/watch?v=c6Mx2mxpaCY
1•KnuthIsGod•55m ago•1 comments

Slop News - The Front Page right now but it's only Slop

https://slop-news.pages.dev/slop-news
1•keepamovin•1h ago•1 comments

Economists vs. Technologists on AI

https://ideasindevelopment.substack.com/p/economists-vs-technologists-on-ai
1•econlmics•1h ago•0 comments
Open in hackernews

A client wants to buy old SaaS app – smart move or risk?

6•AbbeyRoadRunner•7mo ago
We’re a small software house that’s been developing a niche SaaS platform for cultural events over the past 15 years. The product works well, but we were thinking to rebuild it for the next year.

Recently, a well-known national brand — not in tech, but operating in retail — approached us. As part of their PR strategy, they run a medium-sized cultural festival once a year in their home country.

They want to use our platform — but with a hard no to licensing. They’ve had bad past experiences where vendors either raised prices or disappeared, leaving them stranded.

We’re currently in a bidding process, alongside other companies. From what we understand, most competitors are creative agencies likely to: • build something from scratch, or • white-label past projects from similar events.

We estimate that building this kind of event app from scratch would cost around $60,000.

The options we’ve considered so far are:

1. Give them a snapshot of our current codebase, with no support, onboarding, or guarantees. This isn’t ideal — they would need to hire someone else to burn time understanding the architecture and logic before they could even begin implementing or customizing it. It’s slow and wasteful, considering we already know the product inside-out. 2. Give them a snapshot of the code and charge separately for the extra features they’ve asked for (that we don’t yet support). Based on our estimates, development would cost them between $13,500 (optimistic) and $38,000 (pessimistic) if done externally. 3. Same as above, but instead of giving them the code directly, we place it in escrow with a law firm of their choice. If we go out of business, or suddenly triple our rates to lock them in, they’d have the right to release the source and continue working with another vendor. This gives them peace of mind without requiring a full transfer up front.

*Ask HN: What would you do in our shoes?* Any strategic, technical, or legal insights are welcome. Has anyone navigated something similar?

Comments

eschneider•7mo ago
You're going to HAVE to give them support, if only to get them setup. Think long and hard if selling this sort of on-prem version of your product makes sense for YOU. If not, it's likely going to be an expensive distraction and just tell the customer no, you don't sell and support product X that way.

They very likely will be back and if not, no hard feelings.

AbbeyRoadRunner•7mo ago
It does have much sense what you say. So 1. is off the table.

What I am pondering on is how much is worth the IP or to take it from another angle - how much should I charge for it as it's ready now (so we can ship it tomorrow vs. they have to wait for development) + it has been tested in the field so most of QA phase is gone.

nivertech•7mo ago
1. Just agree to not raise the prices above some inflation-linked index.

2. Giving commercial project AS-IS without support is a no-no, and might be illegal in some jurisdictions.

3. Sell them a bank of on-prem support hours.

csomar•7mo ago
I don't know about your circumstances but if I was small, I would completely disregard this.

> We’re currently in a bidding process, alongside other companies. From what we understand, most competitors are creative agencies likely to: • build something from scratch, or • white-label past projects from similar events.

They are not interested in you. They just reached out to platforms to do price/feature/whatever discovery. They might decide on one of them, go with a friend or do nothing.

Do you want to expand time on this? Again, I don't know about your circumstances and don't have much info beyond what you are giving us but I wouldn't.

HenryBemis•7mo ago
What is the(ir) reputation? Do they delay payments? Do they try to find reasons not to pay?

I will oversimplify this (and I work like this when I have to pick a service (anything from SaaS to hiring one of them Big4+2 for a project): I want jeans. I look around. I buy jeans. I am willing to pay full price for jeans. I give proper project reqs/scope of work up front. If they fuck up, I fuck them usiny with the SLA/OLA. I also shit on them to anyone who ever brings them back (with real and damning info). If they do a good/great/their job, I "marry" them until the end of time.

If these guys "appreciate" you what you are, go for it. If they make you jump through 100 hoops then a) tht already picked option Z and they want the rest of you to voluntarily drop out of the race either through pricing (keep adding reqs and keeping the price fixed), or through features (keep adding reqs that they KNOW/sense you cannot deliver e.g. 'oh your app doesn't do liquids? too bad we wanted espresso to go with it).

Either way.. (and judging by the numbers you provided): - from scratch 60k - enhance 13k-38k

Even at the lower end (13k) it is still (almost) 25% of the whole thing..

Doesn't look like a good deal for you.

AbbeyRoadRunner•7mo ago
1. Don't know anything about their rep. Big corp, that's all we know.

2. I do think they appreciate, we offer what they need in time which suits them. That's only my opinion TBH, they said twice that amongst other offers some bidders also have a ready-to-launch product. Maybe it's true, maybe it's a bluff.

3. Yeah, I was thinking about 50% more which makes it 27k $. Or maybe it should be 100%? I am balancing between not beeing greedy, and having a fair cut.

smart10xgenius•7mo ago
Let it go. Your IP is embedded in the platform and too many unknown outcomes post sale.

Also, you will absolutely will be forced to provide support. Maybe not in the contracting document but by the regulators.