Streaming ingest architecture
Events land on a stream, are enriched in flight, and are written to both a lake and a search index.
Every resource, and what it costs.
Projections from August 2026 list prices for always-on resources. Connect an account and these become the figures your provider actually bills.
| Node | Type | What it is | Projected |
|---|---|---|---|
| Ingest endpoint | Network | 10M requests | $10/mo |
| Kinesis Data Stream | Messaging | 2 shards | from $22/mo |
| Enrich and route | Compute | 5M invocations · 512 MB · ~150 ms | from $8.00/mo |
| S3 data lake | Storage | 1 TB standard | $24/mo |
| Search index | Database | t3.small.search | $27/mo |
| Dead-letter queue | Messaging | low volume | $0.50/mo |
Agent steps are priced from provider-reported token usage once the agent runs, not estimated. Guardrails cost nothing and are the reason a runaway agent cannot. 2 rows show from because those services bill by usage, so the total is a scenario at the stated volumes, not a quote.
Similar templates.
Nightly batch ETL
Scheduled extract and load from source systems into a lake, then modelled into a warehouse.
Analytics warehouse
Lake, warehouse and BI, with archival storage for anything older than the retention window.
Open Streaming ingest on the canvas.
It loads as an editable graph. Connect an account or instrument an agent and the projected figures above become measured ones.