---
title: Get started with InfluxDB 3 Cloud
description: InfluxDB 3 Cloud is the fully managed, cloud-hosted version of InfluxDB 3 Enterprise. Learn how to get started writing and querying time series data with InfluxDB 3 Cloud.
url: https://docs.influxdata.com/influxdb3/cloud/get-started/
estimated_tokens: 599
product: InfluxDB 3 Cloud
version: cloud
publisher: InfluxData
canonical: https://docs.influxdata.com/influxdb3/cloud/get-started/
date: '2026-07-14T10:01:19-05:00'
lastmod: '2026-07-14T10:01:19-05:00'
---

InfluxDB 3 Cloud is the fully managed, cloud-hosted version of[InfluxDB 3 Enterprise](/influxdb3/enterprise/).
InfluxData provisions and operates the underlying infrastructure, so you can
write and query time series data without running or scaling servers yourself.

This guide walks through the basic steps of getting started with
InfluxDB 3 Cloud, including the following:

1. [Set up InfluxDB](/influxdb3/cloud/get-started/setup/)
2. [Write data](/influxdb3/cloud/get-started/write/)
3. [Query data](/influxdb3/cloud/get-started/query/)

#### InfluxDB 3 Cloud is in early access

InfluxDB 3 Cloud is currently available to select customers through an
early access program and isn’t yet generally available.
Early access provides a focused subset of InfluxDB 3 Enterprise
capabilities as a managed service.
Availability, features, and workflows may change before general availability.

## Data model

The InfluxDB 3 Cloud server contains logical databases; databases contain
tables; and tables are comprised of columns.

Compared to previous versions of InfluxDB, you can think of a database as an
InfluxDB v2 `bucket` or an InfluxDB v1 `db/retention_policy`.
A `table` is equivalent to an InfluxDB v1 and v2 `measurement`.

Columns in a table represent time, tags, and fields. Columns can be one of the
following types:

* String dictionary (tag)
* `int64` (field)
* `float64` (field)
* `uint64` (field)
* `bool` (field)
* `string` (field)
* `time` (time with nanosecond precision)

In InfluxDB 3 Cloud, every table has a primary key–the ordered set of tags
and the time–for its data.
The primary key uniquely identifies each series and determines the sort order
for all Parquet files related to the table. When you create a table, either
through an explicit call or by writing data into a table for the first time, it
sets the primary key to the tags in the order they arrived.
Although InfluxDB is still a *schema-on-write* database, the tag column
definitions for a table are immutable.

Tags should hold unique identifying information like `sensor_id`, `building_id`,
or `trace_id`. All other data should be stored as fields.

[Set up InfluxDB](/influxdb3/cloud/get-started/setup/)

#### Related

* [Administer InfluxDB 3 Cloud](/influxdb3/cloud/admin/)
* [Write data to InfluxDB 3 Cloud](/influxdb3/cloud/write-data/)
* [Query data in InfluxDB 3 Cloud](/influxdb3/cloud/query-data/)