Quick Answer
JSON Server turns a db.json file into a REST API on localhost:3000. Perfect for solo prototyping. Requex.me takes the same idea, declarative routes and responses, and runs it on a hosted URL your whole team and CI can hit. No localhost, no tunneling, no port conflicts.
JSON Server Alternative, Hosted and Shareable
JSON Server is beloved for good reason: point it at a JSON file and you have a REST API in 30 seconds. But the localhost-only design means the second someone else needs to use it, you are reaching for ngrok or setting up a VM. Here is the hosted path.
JSON Server in 30 Seconds
# db.json
{
"users": [{ "id": 1, "name": "Alice" }],
"posts": [{ "id": 1, "title": "Hello" }]
}
# terminal
npx json-server db.json
# → http://localhost:3000/users
# → http://localhost:3000/postsAuto-generated CRUD endpoints. Great for prototyping. Fails the moment you need to share the URL.
JSON Server Limitations
- Localhost only. Need a teammate or CI to hit it? Add ngrok (free, rate-limited) or a VPS.
- Port conflicts. Every project wants port 3000.
- No auth simulation. Want to test "401 when token missing"? Write custom middleware.
- Static responses. Conditional logic ("return 429 on every 5th request") requires a custom route handler.
- No HTTPS. Frontends running on HTTPS cannot hit HTTP localhost without browser overrides.
- Not persistent. Kill the process, restart, usable, but the URL changes if you reboot.
Requex.me as a Hosted JSON Server
Same model, declare routes, attach JSON responses, on a hosted HTTPS URL:
- Create a mock server in the dashboard
- Add a route:
/users, method GET, body = JSON array - Add more routes as needed
- Share the URL, your mock is at
https://requex.me/mock/{id}/users
No local process. HTTPS from day one. URL survives restarts and works in CI jobs.
Feature Comparison
| Feature | JSON Server | Requex.me |
|---|---|---|
| Hosted URL | No (localhost) | Yes |
| HTTPS | Manual setup | Built-in |
| Auth simulation | Custom middleware | Built-in (Bearer, HMAC, etc.) |
| Conditional responses | Custom middleware | UI builder |
| Auto CRUD from file | Yes | Manual per route |
| Persistent mutations | Yes (writes to db.json) | No (stateless) |
| Price | Free OSS | Free |
When to Use Which
Stay on JSON Server if:
- You want auto-generated CRUD from a flat file
- You need persistent state during your dev session (writes go to
db.json) - Your mock only needs to be accessible to you on your machine
Switch to Requex.me if:
- Your team or CI needs the same mock URL
- You need HTTPS without adding a proxy
- You need auth simulation without writing middleware
- You need conditional responses (different body per request)
- You want the mock to survive laptop reboots
FAQ
Can Requex auto-generate CRUD from a spec?
Yes via OpenAPI import, upload a spec and Requex creates routes and example responses automatically. Flat-file (db.json) import is not supported; convert the file to an OpenAPI spec first, or add routes manually.
Do POST requests persist in Requex?
No, Requex mock responses are stateless. Every request to the same route returns the configured response. If you need stateful mutations (POST adds a record that later GET returns), stay on JSON Server or use a real backend.
Is Requex faster than running JSON Server?
Local JSON Server has near-zero latency. Requex is hosted, so typical latency is 50–200ms. For frontend development this is indistinguishable; for perf tests, local wins.