Nightly batch ETL architecture
Scheduled extract and load from source systems into a lake, then modelled into a warehouse.
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 |
|---|---|---|---|
| Nightly schedule | Messaging | 2M events | $2.00/mo |
| Extract jobs | Compute | 5M invocations · 512 MB · ~150 ms | from $8.00/mo |
| Raw zone | Storage | 1 TB standard | $24/mo |
| Transform ×2 | Compute | 2 × 1 vCPU · 2 GB | $72/mo |
| Redshift Serverless | Database | 8 RPU · ~25 h/month | from $75/mo |
| CloudWatch logs | External | 30 GB ingested | $18/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.
Streaming ingest
Events land on a stream, are enriched in flight, and are written to both a lake and a search index.
Analytics warehouse
Lake, warehouse and BI, with archival storage for anything older than the retention window.
Open Nightly batch ETL on the canvas.
It loads as an editable graph. Connect an account or instrument an agent and the projected figures above become measured ones.