Skip to main content

Glossary

What do bronze, silver, and gold mean in data pipelines?

Last updated Monday, Aug 3, 2026

Bronze, silver, and gold are the traditional names for the three layers of medallion architecture: raw source data, cleaned and validated data, and business-ready aggregates. OptimaFlo uses those same three layers but calls them Raw, Clean, and Ready in the product and user-facing docs, keeping bronze, silver, and gold as internal names only.

Where the color names come from

Bronze, silver, and gold describe a progression in refinement, the same metaphor as medal tiers: each layer is a step closer to something trustworthy and ready to use. Bronze is the least refined, data as it arrived. Gold is the most refined, aggregated and business-ready. The naming predates any single vendor and shows up across the data engineering industry.

What they map to in OptimaFlo

Traditional nameOptimaFlo nameWho owns the work here
BronzeRawThe Data Engineer role lands each connected source untouched
SilverCleanThe Analytics Engineer role writes and version-controls the SQL
GoldReadyDashboards and reports read from this layer directly

For what each layer actually does and why the three-layer split matters, see medallion architecture.

Related terms

Frequently asked questions

Bronze, silver, and gold read as internal engineering jargon. Raw, Clean, and Ready describe what each layer actually is in plain language, so anyone looking at the product, not just an engineer, understands what they're looking at.

Yes, as internal names. Table prefixes and catalog names still use bronze, silver, and gold; the user-facing product and docs use Raw, Clean, and Ready.

Not in OptimaFlo's architecture. It's three layers, Raw, Clean, and Ready, each with a fixed job.

Browse every term or see the AI data team roles.

Staffed, not self-serve

See AI teammates work on your own data.

Now in early beta. One flat plan, no per-query tax. Runs in your cloud, and your tables stay in your account.