Skip to content
CosmoTrace
Menu

Platform · CosmoLake

Your bucket. Your region. Open files. One query engine over both tiers.

CosmoLake is where customer-owned stops being a slogan. Files are written in an open columnar format to object storage you control. Retention is a policy per class. Deleting is a file operation. Leaving is a copy, because there is no proprietary index to export from.

Storage and query

Hot when it matters, cold by default

CosmoLake: open files on your bucket, one query over hot and cold The writer lands open columnar files into a bucket in your account and region. Hot files are indexed; cold files are written directly. A query sweeps both tiers. A file copies out to any reader without CosmoTrace in the path. Animated; static when reduced motion is requested. CosmoStream classed, coordinated YOUR BUCKET · YOUR REGION eu-west · s3://acme-telemetry writer open columnar hot indexed · evidence and search index cold object storage · economy writes here directly query both tiers · one hierarchy 9 files · 2 hot, 7 cold · 41 ms leaving is a copy · any reader, no CosmoTrace in the path measured: 15 MB/s per vCPU · ≤20 vCPU-h per TB landed
Files land in your bucket, hot indexed and cold direct; one query sweeps both; a copy leaves without CosmoTrace in the path. Static if your system asks for reduced motion.

Ownership

What you can do because the files are yours

Read them with anything
The files are standard columnar objects. Your existing query engine, notebook or warehouse can read them without CosmoTrace in the path.
Pin them to a region
The bucket is in the region you choose. On your hardware, it is on your network. Residency is a property of where the bucket is, not a contract clause.
Delete on your terms
Retention is a policy per class and per hierarchy level. Expiry is a lifecycle rule on your storage. A legal hold is a bucket setting you already know how to make.
Leave without an export
If you stop paying us the files are still yours, still readable, still in place. There is nothing to migrate.

Limits

Measured ceilings

15MB/s
Ingest per vCPU

About 1.3 TB per day per vCPU.

≤20vCPU-h
Per terabyte landed

Write, compact and index.

10–100TB/day
Per cell

A cell is one stream and one lake; estates run many.

First-party measurement. CosmoLake absorbs CosmoStream at 400 GB/day per vCPU without a growing lag; that is the property the two numbers are chosen to show.

Managed or on your hardware — the price model is on one page.

Per node with usage overage when we run it; capacity bands when you do. No numbers until we have seen your estate, and no per-gigabyte ingest fee in either case.

Read the pricing modelRequest a demo