Serverless InfluxDB
Time-series for metrics, telemetry, and observability. HTTP write endpoint, query in SQL or InfluxQL, the same Influx tooling you already use.
Tables
- users
- events
- orders
- sessions
| id | name | created_at |
|---|---|---|
| 1247 | signup | 2026-03-12 14:21 |
| 1246 | purchase | 2026-03-12 14:08 |
| 1245 | login | 2026-03-12 13:55 |
| 1244 | signup | 2026-03-12 13:44 |
| 1243 | purchase | 2026-03-12 13:30 |
Pro engine
$15/mo flat, no meters
Encrypted
TLS on every plan
Layerbase Cloud
Managed, in seconds
Desktop and CLI
Run it locally or self-host
Branching
Branch InfluxDB for every preview deploy
Fork a running InfluxDB into a full, isolated copy with its own connection string. Copy-on-write makes it near-instant, not a dump and restore: point a preview deploy at it, test a migration, then throw it away when the pull request merges. Layerbase branches 16 engines, not just Postgres.
See how branching workslbase cloud branch app-db pr-482
lbase cloud branch ls app-db
lbase cloud branch delete app-db pr-482Quick start
Connect with any InfluxDB client
Metrics, telemetry, IoT, observability backends, application performance monitoring, and any workload organized by timestamp.
- Ingest application metrics via HTTP without managing a dedicated TSDB
- Store IoT device telemetry with retention policies and downsampling
- Build a Grafana-friendly observability backend on the same platform as your databases
- Per-environment time-series stores for production-shaped staging
- Self-host on your own hardware with the Layerbase CLI when compliance requires it
curl -H "Authorization: Token YOUR_TOKEN" "https://your-host.cloud.layerbase.dev/ping"
Where to run it
Cloud, desktop, or self-host
One database, three places it can live. Pick the speed you want and move between them when you outgrow it.
Managed InfluxDB hosting
What managed InfluxDB costs here, and how you query it
InfluxDB is a Pro engine on Layerbase Cloud: the floor is the $15/mo Pro plan, flat, with no per-write and no per-query meter. It runs always-on rather than sleeping. The part worth reading before you commit is how queries reach it.
InfluxDB needs the Pro plan, $15/mo
Pro is $15/mo flat: 10 databases, 25 GB of storage, up to 500 concurrent connections, and a 1.5 GB always-on pool. Creating an InfluxDB draws 256 MB of that pool, the smallest draw of any Performance engine here, and pool blocks stack at $10/mo each for another 1 GB of RAM, 1 vCPU, and 25 GB of storage.
Always-on, so a metrics writer never hits a sleeping database
InfluxDB never hibernates here and is never auto-archived, so a Telegraf agent or a scrape loop that goes quiet does not come back to a cold start.
Writes over HTTP, queries in SQL or InfluxQL
Layerbase Cloud runs InfluxDB 3. Telegraf and any client that speaks Line Protocol over HTTP write to the published endpoint, including the v2-compatible write paths. For reads, use SQL or InfluxQL over the v3 HTTP API: the official SDKs query over Arrow Flight, which is gRPC, and that path is not routed on the hosted endpoint. The dashboard snippets show the HTTP calls that do work. Flux was a 2.x language and is not part of InfluxDB 3 at all.
Branch a time-series database
InfluxDB is branchable here: take a copy-on-write copy of the running database in seconds, test the retention change or the downsampling job against it, and delete it afterwards. Pro allows 10 branches per database, and a branch does not consume a slot from your plan database count.
Nothing expires, and backups are automatic
Auto-archiving is a free-tier sweep, so a Pro database is never archived however long it sits. Pro takes a daily backup with 30 days of rolling retention, plus 10 manual slots you trigger yourself, and restore is one click from the dashboard onto the same database or into a new one.
InfluxDB needs the Pro plan, $15/mo flat, with a 7-day free trial. Pool blocks add capacity at $10/mo.
FAQ
Common InfluxDB questions
What is InfluxDB?
InfluxDB is a time-series database for metrics, telemetry, and observability data: everything is organized by timestamp and written over HTTP with the Line Protocol. Telegraf and the official client SDKs speak it directly, which is why it turns up behind so many IoT and application-monitoring stacks. Layerbase runs it as a managed database with an HTTP write endpoint, SQL and InfluxQL query support, and a web console.
How much does managed InfluxDB hosting cost?
InfluxDB is a Pro engine on Layerbase Cloud, so the floor is the $15/mo Pro plan; it is not on the Free plan. Pricing is flat with no per-write or per-query meter, and the cost preview in the create flow shows the monthly cost before you provision anything.
Do I query InfluxDB on Layerbase with SQL or InfluxQL?
Layerbase Cloud runs InfluxDB 3, which you query with SQL and InfluxQL. Flux was an InfluxDB 2.x query language and is not part of InfluxDB 3, so the console exposes the SQL and InfluxQL paths.
Will Telegraf and the official clients work?
For writes, yes: Telegraf and any client that speaks Line Protocol over HTTP write to the published endpoint, including v2-compatible write paths. For queries, use SQL or InfluxQL over the v3 HTTP API; the official SDKs query over Arrow Flight (gRPC), which is not routed on the hosted endpoint, and the dashboard snippets show the HTTP path.
How do retention and downsampling work on hosted InfluxDB?
Retention is configurable per database through the dashboard or the InfluxDB HTTP API (InfluxDB 3 replaced v2 buckets with databases). Default retention settings cover typical observability workloads.
Is there a free InfluxDB tier on Layerbase?
No. InfluxDB is a paid-tier engine on Cloud, starting at the $15/mo Pro plan. The cost preview in the create flow shows the monthly cost before you provision, and the Free plan covers the Standard engines for prototyping.
Can I run InfluxDB locally?
Yes. The Layerbase CLI and Layerbase Desktop both run InfluxDB with the same install workflow.
Branch InfluxDB in seconds
Fork a running InfluxDB into a full, isolated copy with its own connection string. Copy-on-write makes it near-instant, not a dump and restore. Point a preview deploy at it, test a migration, then throw it away. Layerbase branches 16 engines, not just Postgres.
See how branching worksTry InfluxDB free for 7 days
InfluxDB runs always-on from your Pro pool, so it lives on the Pro plan. Start a 7-day Pro trial to spin one up: a card is required, you are charged $0, and you can cancel before it converts to $15/mo. One trial per account.
Start the Pro trialWhat you get
Everything a InfluxDB database should ship with
The same primitives on every InfluxDB database: TLS, web console, hibernation, and a real dashboard. The rows that need a paid plan say so on the row; nothing here is hidden behind a sales call.
Web IDE
Query console in the dashboard, no extra client to install.
TLS by default
All connections encrypted. No setup required.
Always-on connections
Pin a database to your plan's always-on pool so it never hibernates. Free has no pool, so a free database always sleeps when idle; Solo includes 768 MB of pool and Pro 1.5 GB.
Scale to zero
Hibernates when idle. Wakes on the next connection.
Connection pooling
Pooled endpoint for serverless and edge workloads.
Direct connections
Bypass the pooler for migrations and replication.
Native HTTPS endpoint
Engines whose own wire protocol speaks HTTPS. Every database, including this one, is also queryable over the platform's HTTPS query API and web console.
Serverless driver
Drop-in HTTP driver for edge runtimes (Neon serverless, PlanetScale, Upstash REST, or the engine-native client).
IP whitelisting
Restrict access to specific IPs or CIDR ranges.
Automatic backups
Scheduled dumps and volume snapshots with one-click restore on paid plans. Free includes 1 manual backup slot you take and restore yourself.
What it costs
What InfluxDB costs on Layerbase
Plans are flat. There is no per-hour compute meter, no per-database line item, and no ingress or egress fee, so the bill does not change shape when your traffic does. You do not need an AWS, GCP, or Azure account either: Layerbase runs the infrastructure.
Every engine, plus a bigger always-on pool.
Side by side
Hosted InfluxDB, compared
| Provider | Free tier | Billing |
|---|---|---|
| InfluxDB Cloud Serverless | Writes capped at 5 MB per 5 minutes, and data is retained 30 days | Usage-metered: $0.0025 per MB written, $0.012 per 100 queries, $0.002 per GB-hour stored |
| Layerbase | InfluxDB is a Performance engine on Pro | $15/mo flat as 1 of 10 databases, always-on from your pool. No meters. |
InfluxDB Cloud Serverless
- Free tier
- Writes capped at 5 MB per 5 minutes, and data is retained 30 days
- Billing
- Usage-metered: $0.0025 per MB written, $0.012 per 100 queries, $0.002 per GB-hour stored
Layerbase
- Free tier
- InfluxDB is a Performance engine on Pro
- Billing
- $15/mo flat as 1 of 10 databases, always-on from your pool. No meters.
Competitor facts verified September 7, 2026 against each vendor's own pricing and documentation pages: InfluxDB Cloud Serverless.
More on InfluxDB
All articles- August 28, 2026
The InfluxDB 3 Core 72-hour query limit: what it is, why it exists, and your two ways out
InfluxDB 3 Core refuses queries that touch more than 432 Parquet files, which at the default 10-minute file duration works out to about 72 hours of data per query. The data is still there. Here is the mechanism, the knob, what Layerbase actually runs, and the two honest exits.
Read - August 15, 2026
Branching time-series databases
Nobody branches a time-series database. Neon branches Postgres, PlanetScale branches MySQL, and telemetry data gets a stale CSV sample. QuestDB and InfluxDB branch on Layerbase now, and it changes how you test against real metrics.
Read - June 14, 2026
Branching with any database
Neon branches Postgres. PlanetScale branches MySQL. Layerbase branches all of them, because branching happens at the filesystem, not inside the engine. Here is how it works.
Read - March 13, 2026
Best Database for IoT
A practical guide to picking the right database for IoT sensor data, covering QuestDB, InfluxDB, and PostgreSQL with SpinDB examples you can run locally.
Read - March 11, 2026
QuestDB vs InfluxDB
A side-by-side comparison of QuestDB and InfluxDB for time-series workloads, with identical sensor pipelines in TypeScript to show how different they are.
Read
Upstream project
InfluxDB is developed by the InfluxDB project. Layerbase packages and hosts official releases; the engine itself is built upstream.