EmuView

Runs entirely on Cloudflare Workers

Your backend, running at the edge.

Collections and files, multilingual content, GIS data and structured JSON. Authentication with full RBAC. Notebooks, reports and AI assistance. One API, deployed to every region at once.

npx emuview init emu-watch

330+

edge locations

38 ms

median read

0

servers to run

MIT

open source

One API for every kind of data

Records, files, translations and geometry answer the same way, with access control applied before anything leaves the edge.

collections Schema, records, per-field rules
files Containers in R2, thumbnails on upload
geo Points and polygons, queried by bounds
auth Roles, crews, shares and never-rules
Request Response
GET /api/v1/collections/sightings
    ?filter[verified]=true
    &near=151.21,-33.87,25km
    &lang=noongar

{
  "species": "Dromaius novaehollandiae",
  "point": [151.21, -33.87],
  "photo": "photos/IMG_2041.jpg",
  "verified": true
}

Notebooks

A notebook is an install document: one file that declares what it needs, and installs itself into an instance as a plugin.

Lens

Build a page or report over your collections and publish it to a group or to the public.

Flocks

Group people by association, then share to the group instead of to each person.