# TessariDB Cloud

> A TessariDB database and an S3 bucket of your own, on our cluster, behind one account. Early access.

TessariDB Cloud runs our own products for you: a TessariDB database in a namespace of your own and an S3 bucket, both reached over TLS with credentials that reach nothing else.

Sign-in is open now. Creating a database and a bucket arrives with the panel.

## What you get

### A TessariDB database of your own

A namespace with your prefix on our cluster, its own user, reached from anywhere over TLS at db.tessaridb.cloud:9080. Any TessariDB client connects to it.

### An S3 bucket of your own

A bucket in our shared TessariDB S3 with a key that reaches only it, at s3.tessaridb.cloud. Any S3 client works with it.

### One account for both

Signed in at id.tessaridb.cloud, our own sign-in server: a password that has not been seen in a breach, and a second factor.

## How it is built

The databases run on TessariDB, the buckets on TessariDB S3, the accounts on TessariDB OAuth. Customer databases sit on their own node: the address you connect to leads to no other service's data. Every public name answers TLS 1.3 only, and every night each store is backed up and its backup verified.

- [TessariDB](https://tessaridb.com) · [docs](https://docs.tessaridb.com)
- [TessariDB S3](https://s3.tessaridb.com) · [docs](https://docs.tessaridb.com/s3)
- [TessariDB OAuth](https://oauth.tessaridb.com) · [docs](https://docs.tessaridb.com/oauth)
- [TessariKV](https://kv.tessaridb.com) · [docs](https://docs.tessaridb.com/kv)

## Status

The first slice is one cluster on one hardened host. Planned, and not here yet: billing, and deployments of our products of your own, run for you. When something here changes, this page says so.

## Sign in

Accounts live at https://id.tessaridb.cloud/tessaridb. Sign in at https://tessaridb.cloud/auth/login.