Apeeye
github.com/ibr0r0/apeeye- Category
- Developer Tools
- Rank
- No. 3545Tools index
Previous survey · No. 3370 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Coding
- Interfaces
- Web · API
- GitHub
- 6 stars
- Date
About
Apeeye is a browser-based mock REST API tool that lets developers create fake endpoints, such as /users or /posts, instantly with no login, setup, or backend database required. All data is stored client-side in the browser's IndexedDB, and a stateless relay server makes the endpoints reachable from curl, Postman, or another machine, with support for exporting and importing whole workspaces as JSON.
At a glance
Apeeye turns browser-held example data into REST endpoints your frontend or another machine can call. Collections and records live in IndexedDB; a relay forwards incoming requests to the open workspace tab and returns its answer. You can exercise a real HTTP integration before building the backend, provided that tab stays open.
Good fit
Try it for a frontend prototype or a short demo that needs editable fake users, products or orders. The browser test loaded the supplied examples and retrieved four users from a separate tab. Closing the workspace produced an offline error; reopening it restored the response, making the hosting tradeoff concrete.
Consider something else when
You need an always-on backend, authenticated access controls or storage for real customer data. Anyone with the workspace URL can read and write its mocks. Browser storage does not keep responses private from the relay or the clients that request them.
Start here
Open Playground and choose Load examples. Call the displayed /users endpoint from another tab or your frontend and keep the workspace tab open. Requests appear in Activity. Once that fits your workflow, replace the examples with synthetic data of your own and export the workspace JSON as a backup.
Cost and requirements
The public playground opened without login or payment. It needs browser storage and a live relay connection. The source is MIT-licensed; operating your own deployment involves the web frontend and Cloudflare Workers/Durable Objects, whose hosting terms and costs are separate from the source licence.
Limits to know
The in-app docs cap a workspace at 100 collections, with 500 records per collection and 5 MB per record. The newest workspace tab takes over the relay connection. Closing it interrupts endpoints, and clearing browser storage can remove the underlying mocks. Export and import provide workspace backups; this is not durable server storage.
Tags
Tech Stack
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.