nowfound

Alternatives

Products that do what 🌱 Seedpress - NodeJS CMS does

Headless CMS built in Express for PostgresQL using Sequelize

  1. 1
    Rocketgraphâ–²121

    Build production grade web applications in minutes

    2024

  2. 2
    Gridsomeâ–²91

    A Jamstack framework for Vue.js, build apps fast by default

    2021

  3. 3
    expressCartâ–²112

    A fully functional Node.js shopping cart

    2018

  4. 4

    A serverless NextJS/React template to build GPT-3 apps

    2021

  5. 5
    SEEDâ–²106

    100x faster serverless deployments

    2021

  6. 6
    Vendureâ–²98

    Open-source headless e-commerce framework for developers

    2021

  7. 7
    ZappJSâ–²184

    code generator for Node.js, Ruby, Swift, Java, PHP & more

    2018

  8. 8
    Postivaâ–²155

    Easy-to-use headless CMS

    2024

  9. 9
    KeyHippo [LW24]â–²141

    Add API key auth to Postgres Row Level Security (RLS) policy

    2024

  10. 10
    Anyfiddleâ–²145

    Build, run and share code in any language from your browser

    2021

  11. 11EC
  12. 12
    Storipressâ–²149

    All-in-one no code JAMstack publishing platform

    2021

  13. 13
    AstroWPâ–²140

    Headless WordPress starter kit

    2024

  14. 14

    Instantly generate openapi (OAS) 3.0.0 REST + GraphQL APIs

    2019

  15. 15
    Payload CMSâ–²143

    Developer-first TypeScript & React headless CMS

    2021

  16. 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. 17
    Kodinglessâ–²100

    Turn database schema into Backend API source codes

    2023

  18. 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

  19. 19PJ
  20. 20AM
  21. 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

  22. 22NJ
  23. 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

  24. 24JB

Ranked by how close each launch is in meaning, then by votes. Refine with a description →