Alternatives
Products that do what 🌱 Seedpress - NodeJS CMS does
Headless CMS built in Express for PostgresQL using Sequelize
- 1

- 2

- 3

- 4

- 5

- 6

- 7

- 8

- 9
- 10

- 11EC
2012 · github.com
- 12

- 13

- 14

Instantly generate openapi (OAS) 3.0.0 REST + GraphQL APIs
2019
- 15

- 16OS
Hello HN, I built this because I wanted to give Claude Desktop access to my Notion workspace without running a flaky local Python script via stdio. This is a Node.js/Express implementation of the Model Context Protocol (MCP) that uses SSE (Server-Sent Events) for transport. It’s designed to be stateless and deployable as a container (I'm hosting it on Apify, but it works anywhere with Node). The Stack: TypeScript + Express @modelcontextprotocol/sdk Zod for input validation Bearer Auth for security (since it exposes an HTTP endpoint) Capabilities: It allows the LLM to search pages,…
Dec 2025 · github.com
- 17

- 18SO
Hi HN, Over the past year, I’ve been building a native MacOS Postgres client for my personal use. While there are plenty of existing clients, I built this because: - No open-source Postgres client matched the smooth UX of tools like Sequel Pro/SequelAce (for MySQL). - I missed the satisfaction of long-term product ownership and iteration—recent work has me jumping between projects. - I’ve been using Postgres more lately and wanted to get hands-on to deepen my knowledge. I also wanted a playground to experiment with client features that would help me on day-to-day. Some I have…
2025 · github.com
- 19PJ
2019 · github.com
- 20AM
2015 · github.com
- 21TH
Existing headless CMS tools are mostly making it up as they go along - starting with the idea of ‘I want to build a company that delivers a headless CMS’ and then quickly slapping a bunch of technologies together and ending up with a pile of JSONs floating around a MongoDB or another similar frankenstein. As we’d already built the document graph data layer from the ground up, we could properly integrate the CMS features to give a seamless developer experience. We are never going to send you to a screen that says, ‘TerminusCRM requires NodeJS version 10+ and a Mongo database’. It is all…
2023
- 22NJ
2013 · modulus.io
- 23IA
We built InsForge because we wanted to use pure prompts to build a production-grade app faster. In practice, AI isn’t reliable enough when generating code or configuring backend pieces like schema, RLS, auth, or functions. Postgres MCP and Supabase MCP are a good starting point, but they felt more like API wrappers for agents than something designed to guide AI safely through backend tasks. So we built our own MCP server on top of Postgres and added a set of context-engineering tools to make prompt-driven workflows more predictable. It gradually turned into a Postgres-based BaaS. Key…
Nov 2025 · insforge.dev
- 24JB
2015 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →