FlyDBDocs Product
FlyDB documentation

From zero to useful
in minutes.

Familiar SQL on the surface. A watchful operating layer underneath. Here is how FlyDB is designed to fit into your workflow.

flydb create customer-app
Designed workflow

These examples show how FlyDB moves from setup to insight and safe optimization.

01 / Create

One database.
Ready to connect.

Create a database near your users, then receive a familiar PostgreSQL connection string for your application.

Outcome: a secure database endpoint
Terminal
$ flydb create customer-app --region us-east
✓ Database ready in the United States
  postgres://flydb••••@us-east.flydb.dev/customer-app

$ flydb connect customer-app
✓ Connected · TLS enabled
RegionUnited StatesState Healthy
02 / Query

Bring the SQL
you already know.

FlyDB is designed around familiar relational workflows. Create tables, change data, and query it with straightforward SQLite.

Outcome: useful data, without a new language
projects.sql
CREATE TABLE projects (
  id          INTEGER PRIMARY KEY,
  name        TEXT NOT NULL,
  status      TEXT NOT NULL,
  language    TEXT NOT NULL
);

SELECT name, status, language
FROM projects
ORDER BY name;
namestatuslanguage
checkout-apihealthyTypeScript
event-workerhealthyRust
03 / Understand

Ask what changed.
Get the evidence.

Use ordinary language when you need an explanation. FlyDB shows its reasoning and the SQL behind the answer.

Outcome: a cause you can verify
Why did API latency increase after 10:20?
FlyDB analysisHigh confidence

The orders endpoint began scanning more rows as the api_requests table grew. Overall traffic remained within its normal range.

  • EvidenceSequential scan appeared at 10:22
  • Affected queryrecent_endpoint_requests
  • Likely fixIndex endpoint + created time
See diagnostic SQL 
EXPLAIN QUERY PLAN
SELECT * FROM api_requests
WHERE endpoint = '/v1/orders'
ORDER BY created_at DESC;
04 / Improve

Know the impact
before the change.

FlyDB proposes a bounded action, explains its value, and prepares the rollback. You decide when it moves.

Outcome: safer performance improvements
Recommendation FLY–024Low risk

Speed up request history

Proposed SQL
CREATE INDEX IF NOT EXISTS
  idx_requests_endpoint_created
ON api_requests (endpoint, created_at);
Expected impactLess data scanned
Write overheadMinimal
LockingNone expected
RollbackPrepared
Operating principles

Useful by default.
Understandable by design.

01Familiar SQL↗

02Explainable recommendations↗

03Guarded automation↗

04Reversible operations↗

05Visible costs↗