EdgeEver is one of the more complete note-taking projects in this Cloudflare/self-hosting run.

EdgeEver describes itself as an open-source AI-native knowledge base and Evernote alternative with native MCP. The repository ships both Cloudflare and Docker deployment paths, which makes it more flexible than the Cloudflare-only notes apps I covered recently.

The short version:

Cloudflare mode = Workers + static assets + D1 + R2
Docker mode     = Bun + SQLite + local /data resources

That is a useful split. You can treat EdgeEver as a zero-server Cloudflare app, or run it like a normal homelab service.

What is EdgeEver?

EdgeEver is a modern notes and knowledge-base app with an Evernote-like three-pane workflow.

The feature set is broad:

  • rich text and Markdown-style editing;
  • notebook hierarchy and organization;
  • web clipping;
  • files up to 1 GiB with chunked streaming;
  • client-side image compression;
  • visual diagram notes;
  • AI-assisted tables and forms;
  • revisions and exports;
  • password-protected sharing;
  • AI RSS digest;
  • remote MCP and desktop agent integration;
  • bring-your-own AI provider support;
  • web, desktop, mobile, and browser-extension targets.

It is not a tiny capture app. It is closer to a full personal knowledge base with AI and agent surfaces built into the architecture.

Architecture Overview

The stack is modern TypeScript:

Layer EdgeEver Uses
Web frontend React, Vite, React Router, TanStack Query, Tailwind, shadcn/Radix
Editor TipTap / ProseMirror
API Hono and Zod
PWA/offline vite-plugin-pwa, Workbox, Dexie, sync queue
Cloudflare storage D1 and R2
Docker storage SQLite and local filesystem resources
Optional object storage S3-compatible storage in Docker mode
Runtime Cloudflare Workers or Bun self-hosted
Agent access Remote MCP and desktop ACP-style integration

The important implementation detail is that the same Hono API and service layer are used across the Cloudflare and Docker targets. The storage adapters change:

Cloudflare adapter -> D1 + R2
Docker adapter     -> SQLite + /data/resources, or SQLite + S3-compatible resources

That avoids the common problem where the Docker edition feels like an afterthought.

Docker Compose

For a homelab, Docker is the simplest starting point:

services:
  edgeever:
    image: ghcr.io/tianma-if/edgeever:${EDGE_EVER_VERSION:-v1.100.0}
    container_name: edgeever
    init: true
    restart: unless-stopped
    ports:
      - "${EDGE_EVER_PORT:-8787}:8787"
    environment:
      EDGE_EVER_AUTH_USERNAME: "${EDGE_EVER_AUTH_USERNAME:-admin}"
      EDGE_EVER_AUTH_PASSWORD: "${EDGE_EVER_AUTH_PASSWORD:?Set EDGE_EVER_AUTH_PASSWORD in .env}"
      EDGE_EVER_SESSION_TTL_DAYS: "${EDGE_EVER_SESSION_TTL_DAYS:-400}"
      EDGE_EVER_CONTAINER_IMAGE: "ghcr.io/tianma-if/edgeever"
    volumes:
      - edgeever-data:/data
    security_opt:
      - no-new-privileges:true
    cap_drop:
      - ALL
    stop_grace_period: 30s

volumes:
  edgeever-data:

Create the environment file:

cp .env.sample .env
nano .env

At minimum, set:

EDGE_EVER_AUTH_PASSWORD=change-this-long-password

Then start it:

docker compose up -d

The UI listens on:

http://192.168.1.2:8787/

From the host, the health check is:

curl http://127.0.0.1:8787/api/health

In my local test, the container reported:

{
  "ok": true,
  "runtime": "self-hosted-bun",
  "authMode": "required",
  "migration": "0059",
  "storage": {
    "database": "sqlite",
    "resources": "filesystem"
  }
}

The root page also served the EdgeEver web app.

Docker Data Layout

Docker mode persists data under /data inside the container.

The practical files are:

/data/edgeever.sqlite
/data/edgeever-secrets.json
/data/resources/

That makes backups easy:

  1. Stop the container.
  2. Back up the whole Docker volume.
  3. Start the container again.

If you configure S3-compatible attachment storage, remember that SQLite still stays under /data, but newly uploaded resources live in the external bucket. In that setup, back up both the volume and the bucket.

Cloudflare Deployment

The Cloudflare path uses:

Binding Service Purpose
DB D1 Notes, metadata, accounts, settings
RESOURCES R2 Attachments and binary resources
Worker assets Cloudflare Workers Static Assets Built React/Vite frontend
Worker secrets Cloudflare Workers Admin password, credential encryption

A typical Cloudflare deployment needs:

  • a Cloudflare account;
  • Workers enabled;
  • a D1 database, normally named edgeever;
  • an R2 bucket, normally named edgeever-resources;
  • EDGE_EVER_AUTH_PASSWORD as a Worker secret;
  • optionally EDGE_EVER_AUTH_USERNAME;
  • optionally EDGE_EVER_CREDENTIALS_ENCRYPTION_KEY;
  • Wrangler credentials or Cloudflare Git deployment.

The Cloudflare version is the right path when you want no server, no Docker host, and Cloudflare-managed TLS/routing/storage.

The Docker version is the right path when you want local data and ordinary volume backups.

Where It Fits

Project Best Fit
Memos Worker Small Cloudflare-native notes and docs
FlareMo Cloudflare Memos-style workspace with AI/team features
Inkstone Cloudflare-native Markdown notebook
EdgeEver Evernote-style knowledge base with Cloudflare and Docker deployment
Official Memos Docker Traditional Docker notes app

EdgeEver is the most “complete app” of this subset. It has more moving parts than Memos Worker, but it also gives you more: desktop/mobile targets, clipping, attachments, exports, revisions, PWA behavior, AI, and MCP.

FAQ

Conclusion

EdgeEver is not the smallest notes app in this series, but it is one of the most balanced.

It can run as a true Cloudflare app, yet it also gives homelab users a conventional Docker path with SQLite and local files. That combination makes it much easier to recommend than a Cloudflare-only note tool when long-term backup and migration are part of the decision.