Placemark is going open source and shutting down
An online map-editing service, Placemark, is shutting down and releasing its code as open source, prompting reflection on what happens to software and users when small SaaS companies fail. Commenters weigh the benefits and limits of open sourcing a defunct product—especially for hosted tools that are hard to self-run—alongside the realities of IP ownership, acquirer incentives, and niche pricing in the GIS market. The exchange broadens into concerns about subscription fatigue, the difficulty of making indie SaaS sustainable, and whether service-based or FOSS-first models offer more resilient paths for similar tools.
Open-sourcing on shutdown
- Many applaud releasing the code instead of letting it die; seen as rare and user-friendly.
- Others note “just open source it” is not always feasible: IP often belongs to investors/creditors, or is entangled with paid components.
- Some argue that open source mainly helps a subset of users (self-hosters, developers), not typical SaaS customers who paid for a service, not code.
- Security worries: publishing source before shutdown could expose vulnerabilities while the service is still live.
Business and IP incentives
- Early pledges to open source on failure are debated:
- Pros: mitigates “bus factor,” benefits public.
- Cons: may reduce acquisition value and create perverse incentives to prefer failure for a FOSS release.
- Commenters highlight that, at failure, the company may not legally control the code anymore.
Viability of OSS from failed startups
- Question raised: how often do such projects thrive after open-sourcing?
- Several examples (browsers, office suites, 3D tools, frameworks) are cited as counterexamples to skepticism.
- Some note open-source projects can be viable where businesses weren’t, because business overhead disappears.
Pricing, subscriptions, and target customers
- $20/user/month is seen by some as steep for small teams, especially when multiplied across many SaaS tools.
- Others argue the product is niche GIS tooling and should have charged more and gone upmarket/enterprise.
- Several say users unwilling to pay even $10/month are simply not the target market.
- Broader frustration with subscription fatigue: many small SaaS fees accumulate; some people default to avoiding new subs.
Product and technical choices
- Real-time collaborative editing is seen by some as over-ambitious and possibly not demanded.
- Others respond that modern libraries make collaboration relatively cheap to add, though the founder notes it did complicate scaling.
User reactions and alternatives
- Multiple users praise the product’s balance of simplicity and power, especially for GeoJSON workflows.
- Some compare it to or mention alternatives in the GIS/mapping space (e.g., QGIS, other web-based tools, FOSS-first services).
- Government and enterprise GIS are cited as the real money, but require heavy sales effort.
HN redirect and meta-discussion
- The blog’s HN-referrer-to-Google redirect is noticed; some find it clever, others petty.
- After reading the author’s critique of HN culture, some commenters become more sympathetic, though still divided.
Founder economics / bootstrapping
- Typical bootstrapping patterns mentioned: living off savings, consulting on the side, or a partner’s income.
- For small software startups without employees, direct cash losses can be low; the main cost is forgone salary and stability.