← Leaderboard
8.0 L4

Electric Sql

Native Assessed · Docs reviewed · Mar 26, 2026 Confidence 0.54 Last evaluated Mar 26, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Electric Sql quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 26, 2026

Freshness

Updated 2026-03-26T15:54:34.339+00:00

Mar 26, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.1
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

7.8
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

8.0

Autonomy breakdown

P1 Payment Autonomy
G1 Governance Readiness
W1 Web Agent Accessibility
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

ElectricSQL: Comprehensive Agent-Usability Assessment

Docs-backed

ElectricSQL makes PostgreSQL data instantly available client-side — define a "shape" (a filtered view of a Postgres table), and ElectricSQL syncs it to local SQLite in the browser or mobile app in real time. For agents: embed a local SQLite database in agent interfaces that need to work offline, sync agent configuration or state from a Postgres backend without polling APIs, and enable real-time collaborative agent workspaces with automatic conflict resolution. ElectricSQL Electric v2 (2024) uses HTTP long-polling for sync (no WebSocket dependency). Confidence is docs-derived.

keel-expansion Mar 26, 2026

ElectricSQL: API Design & Integration Surface

Docs-backed

TypeScript SDK: npm install electric-sql. Sync shape: import { Shape } from "@electric-sql/client"; const shape = new Shape({ url: "http://electric-host/v1/shape/todos?table=todos&where=user_id%3D123", backoffOptions: {...} }). Subscribe: shape.subscribe(({ rows }) => { setTodos(rows); }). React hook: import { useShape } from "@electric-sql/react"; const { data: todos } = useShape({ url: "http://electric-host/v1/shape/todos" }). HTTP API (Electric server): GET /v1/shape/{shape_name}?table={table}&where={filter}&offset={offset} returns shape data as JSON. SSE: streaming updates via If-None-Match + handle: headers. Shape params: table (required), where (SQL WHERE clause), columns (subset of columns). Local SQLite write: through your own application code + sync back to Postgres via standard API.

keel-expansion Mar 26, 2026

ElectricSQL: Auth & Access Control

Docs-backed

Electric server auth: configurable per deployment (proxy Electric behind your own auth layer). Electric Cloud: API key or JWT. HTTPS enforced. Shape access control: filter shapes by user ID in where clause + validate server-side. No built-in auth in the Electric HTTP API — must proxy through authenticated API gateway. JWT-based auth available in Electric v2 for shape access control. Self-hosted: manage auth at reverse proxy level.

keel-expansion Mar 26, 2026

ElectricSQL: Error Handling & Operational Reliability

Docs-backed

Sync latency: shapes update within seconds of Postgres writes. Offline: local SQLite reads work without network; writes queue for sync on reconnect (v2: optimistic updates via local writes). Conflict resolution: last-writer-wins for simple cases; CRDT-based for collaborative scenarios. Shape invalidation: if where clause changes, Electric issues a must-refetch signal. Large shapes: shapes stream incrementally — initial sync proportional to shape size. Electric server: stateless (can scale horizontally behind load balancer). Postgres dependency: Electric requires Postgres with logical replication enabled. Self-hosted: Docker + Postgres with wal_level=logical.

keel-expansion Mar 26, 2026

ElectricSQL: Documentation & Developer Experience

Docs-backed

electric-sql.com/docs covers shape definition guide, TypeScript SDK reference, React integration, HTTP API specification, and self-hosting with Docker. Getting started: npm install @electric-sql/react — connect to Electric Cloud or self-hosted in 5 minutes. Electric Cloud: free tier. Self-hosted: Docker + Postgres. GitHub: electric-sql/electric (7k+ stars). Community via Discord (active). Good documentation; shape concept is well-explained with visual diagrams.

keel-expansion Mar 26, 2026

Use in your agent

mcp
get_score ("electric-sql")
● Electric Sql 8.0 L4 Native
exec: 8.1 · access: 7.8

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L4 Native

8.0 / 10.0

Alternatives

No alternatives captured yet.