Embedding

Cyyrus

Transform Unstructured Data into Usable Datasets

Wanna help? Awesome! There are many ways you can contribute.

Wanna know what's coming up? Check out our roadmap.

There's a new sheriff in town. And it's called the CLI.

Tasks help you generate data. Think of them like recipes for generating data.

Types are like blueprints for your data. They define the structure of your data and how it can be interacted with.

Datasets are the core of Cyyrus. They are the data that you generate and publish.

Columns are like the building blocks of your dataset.

Schema outlines entire workflow. Think of it as poor man's HCL.

Versioning is important. Here's how you can manage it.

Unf*ck unstructured data. Nothing more, nothing less.

Tap into latent space of Language Models to generate data. And more.

Seed your data from an existing dataset. Be it a CSV, JSON, or a something else.

Scrape it like you mean it. Because you do.

Cyyrus doesn't need a manual, but here's one anyway.

Task ID is a unique identifier for a task. Think of it as a primary key.

Task inputs are the data that a task needs to run. We'll show you how to define them.

You know, the basics. Strings, numbers, booleans, and null.

Object types are used to define a collection of key-value pairs. They are the most versatile type in the schema.

Array types are used to define a list of items of a specific type. Nothing more, nothing less.