Lattice API
neon · production · US East
Dashboard tour
Tour the protected workspace through accessible synthetic previews. See how DatabaseMeter organizes portfolio status, database growth, provider evidence, PostgreSQL workload, planning estimates, alerts, on-demand AI analysis, integrations, and reports—without exposing a user's private dashboard.

No credit card or payment information is required. DatabaseMeter does not charge for the account or dashboard; your database provider may still charge for its own service and usage.
Portfolio overview
The overview combines live projects from supported sources into one operational starting point. It surfaces known size, comparable growth, recent collection state, and projects that meet an explainable attention rule.
Measurement boundary: Totals include only compatible known values. Demo data never appears as live monitoring data.
Projects
8
4 Neon · 4 Supabase
Known size
75.2 GB
Compatible values
30-day growth
+12.1%
Weighted known size
Needs attention
5
Explainable rules
Database inventory
The Databases workspace provides a provider-aware inventory and detailed project pages. Review environment, region, current status, size, trends, recent changes, and the measurements that source actually exposes.
Measurement boundary: Provider labels and unavailable fields remain visible instead of being normalized into misleading equivalents.
neon · production · US East
neon · production · US West
neon · staging · EU Central
Compute
Compute separates provider-native consumption from resource configuration and optional PostgreSQL workload evidence. When telemetry is connected, aggregate query and session statistics can offer investigation clues.
Measurement boundary: Observed PostgreSQL activity is not exact query-level billing attribution, and incompatible provider units are never combined.
Lattice API
8.4 CU-hours
Provider-native period
Orbit Commerce
32.6 CU-hours
Provider-native period
Observed workload context · not billing attribution
Storage
Storage ranks compatible PostgreSQL size observations, shows growth over selected periods, and presents provider resource evidence separately. This helps identify fast-changing databases without confusing logical size, filesystem allocation, WAL, or object storage.
Measurement boundary: Unlike storage scopes are presented separately, and a missing provider value remains unavailable.
Compatible provider API and direct telemetry values
Cost planning
The Costs workspace applies versioned provider rules only when compatible stored observations exist. It exposes the observations, rate source, assumptions, exclusions, and reasons an estimate cannot be produced.
Measurement boundary: Planning estimates are not invoices. DatabaseMeter does not fabricate a cost for unsupported providers or missing allocation evidence.
Example measured usage
$24–$31
Versioned rates · compatible observations · exclusions shown
Unavailable
Compatible compute history and allowance allocation are not available.
Not an invoice forecast. Confirm spending in the provider billing console.
Analysis and alerts
Alert rules evaluate stored metrics against visible thresholds. The workspace shows growth analysis, unresolved and resolved events, synchronization health, and the rule responsible for each finding.
Measurement boundary: Rules do not fire when their required metric is missing; repeated evaluations are deduplicated until resolution.
On-demand AI analysis
The AI analysis workspace offers predefined operational questions for one database, all monitored databases, all Neon, all Supabase, or all other monitored sources. Before each request, it shows the target count and monitoring categories that will be sent.
Measurement boundary: AI analysis is optional, on demand, read-only, rate limited, and advisory. Credentials, connection details, SQL text, application rows, and raw provider responses are excluded.
Learn how DatabaseMeter uses AIAll monitored · 8 synthetic databases · last 24 hours
Overall status
Review
3 findings · evidence linked
Two databases have stale resource evidence, so current infrastructure pressure cannot be determined confidently.
Evidence: DB3-RESOURCE, DB6-RESOURCE · medium confidence
Data boundary: prompt-specific normalized monitoring evidence only; no credentials, SQL text, or customer rows.
Integrations
The integrations workspace manages Neon, Supabase, direct PostgreSQL, and optional per-database telemetry. Connection summaries, capability states, schedules, collection history, diagnostics, credential replacement, pause, refresh, and disconnect controls remain together.
Measurement boundary: Provider API access and PostgreSQL telemetry are independent. Telemetry can create normal provider connection or compute activity.
2 connections
1 connection
3 databases
Connection guidance keeps credential, TLS, permission, and capability diagnostics with the affected setup.
Settings and reports
Settings includes timezone-aware weekly reports, opt-in delivery preferences, recent delivery outcomes, integration access, and permanent account-data deletion. Reports summarize data already stored by DatabaseMeter.
Measurement boundary: Weekly reports are opt-in and never include credentials, connection strings, SQL text, or customer row contents.
America/New_York
Opted in
Monday at 9:00 AM · noteworthy changes only · next delivery shown in your timezone
Start with your own portfolio
Create an account without a credit card or payment information. Connect a provider only when you are ready, and keep provider charges separate from DatabaseMeter access.