brevis.sh valid

brevis.sh

Open source data infrastructure in Go, in four pieces: the **Core** orchestrates

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T04:52:14.744Z. Cached copy · Source on brevis.sh

# brevis.sh

> Open source data infrastructure in Go, in four pieces: the **Core** orchestrates
> (workflows, a persistent queue, a scheduler and an operational interface, in
> one binary that never touches the data); the **SDK** extracts and loads; the
> **Gateway** receives events over HTTP; and **SQL** models tables. A step runs
> as its own Kubernetes pod with its own image, or on a machine you already
> run. MIT licensed.

Every page below is also served as Markdown: append `index.md` to any docs URL.
`https://brevis.sh/llms-full.txt` is this entire documentation set in one file.

How the pieces fit: a **workflow** is a YAML file of **steps**; the
**scheduler** turns schedules into **runs** and a **queue** executes them; each
step becomes a **pod**, or is sent to a **host** you keep running. A step is any
command in any image — the **Go SDK**
(`brevis/sdk`) is for extract-and-load work, and the **client libraries**
(`pip install brevis`) give a step the run's context, clock and metrics through
two environment variables.

There is a third piece with a version of its own: the **ingestion gateway**
(`areteacademy/brevis-gateway`), an HTTP endpoint that lands data which arrives
instead of going to fetch it — configured entirely by YAML, delivering to
Pub/Sub, Postgres, MySQL, BigQuery, Redshift or object storage. What joins all
three is the `ingestion_id`, a frozen UUID v5 over
`provider|entity|source_key|record_ts`: a row the gateway lands and a row an SDK
fetcher lands for the same record are the same row.

The fourth piece, also versioned on its own, is **SQL**
(`areteacademy/brevis-sql`, 0.1.0): plain `.sql` files that stay valid SQL,
built into tables and views in the order their references imply, on Postgres
or BigQuery — `brevis-sql compile`, `graph`, `build` and `test`. No templating.

The same documentation in Portuguese: https://brevis.sh/docs/ (append `index.md` likewise).

## Start here

- [Ecosystem](https://brevis.sh/en/docs/ecosystem/index.md): The four brevis.sh pieces, what each one does, and where the data goes through.
- [Integrations](https://brevis.sh/en/docs/integrations/index.md): What connects to what: where data comes from, where it lands, where it is modelled and where it all runs.
- [Introduction](https://brevis.sh/en/docs/introduction/index.md): What brevis.sh is, the problem it solves, and when it is not the right choice.
- [Installation](https://brevis.sh/en/docs/installation/index.md): How to get the binary, what it requires, and how to confirm the install is correct.
- [Quickstart](https://brevis.sh/en/docs/quickstart/index.md): From nothing to a live DAG in the interface, in four steps.

## Building a workflow

- [Workflows](https://brevis.sh/en/docs/workflows/index.md): The complete YAML format — steps, dependencies, images, resources and schedule.
- [Parameters](https://brevis.sh/en/docs/parameters/index.md): What changes between two runs of the same workflow, without editing the file.
- [Step runtime](https://
…

Machine-readable: GET /v1/resolve?q=brevis.sh · GET /v1/domain/brevis.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for brevis.sh:
1. POST https://agentwebmap.com/v1/sites/brevis.sh/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://brevis.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/brevis.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/brevis.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.