Alternatives
Products that do what middlerok does
Bridges frontend & backend with smart API contracts
- 1

- 2

- 3

- 4AJ
Hey HN, we’re building an open specification that lets agents discover and invoke APIs with natural language, built on the OpenAPI standard. agents.json clearly defines the contract between LLMs and API as a standard that's open, observable, and replicable. Here’s a walkthrough of how it works: https://youtu.be/kby2Wdt2Dtk?si=59xGCDy48Zzwr7ND. There’s 2 parts to this: 1. An agents.json file describes how to link API calls together into outcome-based tools for LLMs. This file sits alongside an OpenAPI file. 2. The agents.json SDK loads agents.json files as tools for an LLM that…
2025 · github.com
- 5

- 6

- 7

- 8

- 9

- 10

- 11AM
2016 · askmacgyver.com
- 12

- 13

- 14

- 15

- 16IO
Hi HN, I'm Mohammed, a technical founder who loves shipping and giving back to the community. I'm open-sourcing the full-stack engine that powers my B2B product, apflow.co. What it is: A production B2B starter with a Go backend and Next.js frontend. Both are fully Dockerized with separate containers. No Vercel. No Supabase. Deploy the whole thing on a $6 VPS, or split frontend and backend across different providers. You own the infrastructure. The problem I was solving: Every SaaS starter I evaluated had the same issue: they locked me into someone else's platform. Vercel for hosting.…
Dec 2025 · github.com
- 17

- 18

I created Pylon to make it easier to move from hobby projects to full production apps. When I work on hobby projects, I usually use React or Next.js because they are quick to set up and easy to deploy on Vercel. For production apps, I separate the frontend and backend, then deploy the backend on AWS. But setting up a full backend on AWS can be complex and costly, especially for simple apps. Pylon is a full-stack, real-time framework that includes server-rendered React, TypeScript functions, entities, policies, real-time sync, built-in authentication, and support for background and scheduled…
Jul 2026 · pylonsync.com
- 19ST
Hey everyone! Over the past two years I threw myself back into full-time engineering with a simple goal: write code that gives back to the community. After a lot of late-night FOMO (“AI will do it all for us, right?”) and some painful production incidents, I finally turned my weekend project into an open-source library. [ What is Solidis? ] - Super-light (< 30 KB) RESP2/RESP3 client with zero runtime deps and first-class ESM/CJS support. - Fully tree-shakable – import only the commands you need. - Written with SOLID principles & full TypeScript typings for every command. - Designed…
2025 · github.com
- 20LE
I've been developing game backends for several years, using and designing a lot of code. They all about calculations, synchronization with front-end data, and database data, and try to ensure consistency, atomicity, and high response, etc. However, these codes and frameworks have always had problems such as very complicated APIs, incomplete or non-existent ACID, multiple calls to RPC, and non-real-time full or semi-full data landing. So, we created Lockval Engine. An easy-to-use, ACID, distributed, DOP, multi-language support backend engine. Here are some online demos that will give you a…
2023 · lockval.com
- 21

- 22NC
Backengine is a tool that evolved from an experiment at my startup for which we wanted to pass structured data to an LLM completion API and receive structured data back. We thought we'd release it as a standalone tool for others who might also find it useful. Backengine lets you create hosted API endpoints for which the endpoint logic is described in natural language as an LLM prompt. The endpoints accept structured requests and return structured responses. Why is this useful? Hosted - no additional infrastructure to maintain. Prompt engineering workspace - you can edit, test and tweak…
2023 · backengine.dev
- 23KA
Hi HN, I’m one of the creators of Keel and we're excited (and nervous in equal measures) to be sharing this. We built Keel on two principles: 1. A backend is much more than just a database. A scalable backend platform should be grounded in engineering best practices and come complete with a full suite of services without having to wire 10 SaaS products together 2. A backend should not be an engineering black box and should be designed from day one to support the entire organisation over time and scale. Keel is a schema driven backend engine. Define your data model, api actions, permissions,…
2024 · keel.so
- 24

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