Personality typing is a time-honoured tradition in tech. You've taken the Myers-Briggs, argued about whether you're really an INTJ, and been sorted into a primary-coloured group that allegedly encapsulates your work persona. But the test nobody was brave enough to publish is the one that actually matters to your daily work: which Dremio feature matches your cosmic archetype?
The twelve signs below have each found their counterpart in Dremio's platform. Some matches are flattering. Some are accurate in uncomfortable ways. And all of them are more useful than Mercury retrograde as an explanation for your pipeline failures.
Explore this interactive demo and see how Dremio's Intelligent Lakehouse enables Agentic AI
Bold. Competitive. Refuses to wait.
Aries doesn't have time for slow queries. Neither does Reflections. Dremio's query acceleration feature pre-computes and caches results automatically, so dashboards load in seconds rather than minutes. No waiting, no excuses, no re-running the same aggregation for the fifth time today.
Reflections are materialised views that Dremio creates and manages on your behalf. You define what you want accelerated, Dremio builds and refreshes it, and from that point every query that can use a Reflection does so without any changes to the BI tool, the SQL, or the analyst's workflow. A report taking 45 seconds to query raw Parquet drops to under a second. Just like Aries charging headfirst into battle, Reflections hits every query at full speed before the competition has even warmed up.
Aries energy: "I already ran that query and cached the result. You're welcome."
Reliable. Stubborn. Built to last.
Taurus is the friend who shows up on time, every time, and never loses your stuff. Apache Iceberg, the open table format at the core of Dremio's lakehouse, was designed with exactly this kind of longevity in mind. Dependable, grounded, and deeply unimpressed by flashy proprietary formats that won't be around in five years.
Iceberg brings full ACID transactions, time travel, schema evolution, and partition evolution to your data lake. Your data stays in open Parquet files on your own storage, under your control. No proprietary formats, no vendor lock-in, no scramble if you need to migrate your query engine in three years. Dremio treats Iceberg not as an optional format but as the foundation: the catalog, the lakehouse management layer, and the write path all sit on top of it natively. Taurus plays the long game, and so does Iceberg.
Taurus energy: "I've been storing your data safely for years. I also brought a snack."
Adaptable. Multi-talented. Comfortable everywhere.
Geminis are equally at home at a dinner party and a board meeting. Dremio's data federation capability works the same way: one SQL interface simultaneously querying S3, Azure Data Lake, PostgreSQL, MongoDB, Snowflake, and dozens of other sources without copying a single byte. Gemini doesn't pick a lane, and neither does Dremio's virtual layer.
This isn't a replication job that runs at 3am and is six hours stale by the morning standup. Dremio federates queries in real time, pushing computation down to each source where possible and assembling results transparently to the user. A single query can join a live operational database against a historical Parquet lake and reference a lookup table in MySQL, all in one pass. It speaks every dialect fluently and somehow makes it look effortless.
Gemini energy: "Oh, your data is in a different source? I'm already there."
Protective. Intuitive. Deeply loyal to their people.
Cancer is the sign most likely to remember your data privacy preferences before you do. Cancer doesn't let just anyone into their home, and neither does Dremio when it comes to your PII.
Dremio's access controls include row-level and column-level security, data masking, and role-based access controls that apply at query time regardless of which BI tool or API is making the request. A standard analyst querying through Tableau sees masked credit card numbers. A user with the right permissions sees the full value. The policy lives in Dremio once, not duplicated across six downstream tools that each need to stay in step. The data is safe. Cancer made sure of it.
Cancer energy: "I've already masked that SSN column. I was worried about it."
Confident. Magnetic. Wants to be understood.
Leo is the star of the show, and the Semantic Layer is where Dremio shines in the spotlight. Leo doesn't do ambiguity. "Revenue" means one thing, it's defined here, and everyone will use it.
The semantic layer is where your business metrics, dimensions, and calculations get defined once. Every BI tool connecting to Dremio reads from the same underlying definitions, so a C-suite dashboard, an ad-hoc analyst query, and an AI agent processing your data are all working from identical logic. By defining metrics, dimensions, and business logic once in a central place, the Semantic Layer ensures every analyst, every dashboard, and every stakeholder is working from the same single source of truth. The room turns to Leo, and every BI tool turns to the Semantic Layer.
Leo energy: "I've already defined what 'active user' means for the whole company. You're welcome."
Analytical. Detail-obsessed. Quietly fixes everything.
Virgo notices the thing nobody else notices. They've already spotted the bottleneck in your execution plan. Virgo doesn't accept "it's just slow" as a diagnosis. They want to know which operator, which join, which stage, and exactly how many milliseconds each part is responsible for.
Dremio's Query Profiles expose the full execution plan of any query: operator-level timing, row counts at each stage, which Reflections were considered and whether they were actually used, memory allocation, and where time was spent. A query taking 12 seconds can be traced to a specific hash join on an unfiltered table, which points directly to a missing Reflection or a missing filter predicate. Virgo doesn't just say a query is "slow." They show you precisely which join took 4.7 seconds and exactly why. This is the feature for engineers who find messy query plans personally offensive.
Virgo energy: "Your query plan has a hash join where a merge join would be 40% faster. I already fixed it."
Balanced. Fair. Believes everyone deserves a seat at the table.
Libra can't stand when one team hoards all the data, and neither can a well-designed data mesh. Libra's problem with most data architectures isn't technical. It's structural.
One central team owning all data products, all pipelines, and all access decisions creates bottlenecks and data that's perpetually six weeks behind what the business needs. Dremio's architecture supports decentralised data mesh patterns by letting domain teams own and manage their own data products while keeping governance centralised. A finance team publishes their revenue models as a governed data product. A marketing team manages attribution data with their own freshness SLAs. Libra is always brokering peace between engineering and the business. Dremio brokers peace between your data domains.
Libra energy: "Marketing gets their own data product. So does Finance. Nobody fights. Harmony."
Intense. Keeps records. Never forgets a thing.
Scorpio remembers everything. Not out of spite, but because having one authoritative record of what exists, where it lives, and who can touch it is simply sound practice. Scorpio keeps receipts. Open Catalog keeps table metadata. Cross either of them at your peril.
Dremio Open Catalog is a managed Iceberg catalog built on the Apache Polaris specification. It serves as the single source of truth for your Iceberg tables, accessible by any engine that speaks the Polaris REST API: Dremio, Spark, Flink, Trino, and others can all read from and write to the same catalog without a coordination layer in between. That means your data engineering team running Spark jobs and your analytics team querying through Dremio are looking at the same tables, with the same governance policies applied, without duplicating the catalog or negotiating access separately. Open Catalog holds the knowledge of your entire Iceberg estate. Nothing gets added, changed, or removed without it knowing.
Scorpio energy: "Spark wrote it, Flink transformed it, Dremio is querying it right now. I know. I always know."
Adventurous. Freedom-loving. Can't be contained.
Sagittarius doesn't do well with constraints. The query goes where the data lives. The adventure never ends.
Dremio's cloud-native architecture separates compute from storage completely. Executor pods scale up when queries arrive and release when the work is done, so you pay for what you consume rather than provisioning a cluster size you hope will cover the peaks. A team running ten queries a day and a team running ten thousand queries a day operate on the same platform with the same governance and the same SQL interface. Dremio on the cloud never asks you to pre-provision a cluster before you go exploring, and it never asks your analysts to wait while the infrastructure catches up with demand.
Sagittarius energy: "I just scaled to 200 executors for that query and back to zero. The cloud is my oyster."
Ambitious. Disciplined. Obsessed with structure.
Capricorn is the one who schedules the maintenance window while everyone else is focused on shipping features. They understand that a lakehouse nobody maintains is a lakehouse that quietly degrades, and they find the people who ignore that fact genuinely baffling. Table maintenance isn't exciting, but Capricorns don't need it to be. They need things to work, on schedule, every time, so that the tables everyone else depends on keep performing months and years from now.
Dremio's table optimization commands, such as OPTIMIZE TABLE and VACUUM TABLE, are the operational backbone of a healthy Iceberg lakehouse. OPTIMIZE compacts the small files that accumulate as data lands in a lake: frequent inserts and streaming writes tend to produce hundreds of tiny Parquet files where a handful of large ones would serve far better. Left unchecked, that file sprawl drives up metadata overhead and slows every query that touches the table. Running OPTIMIZE consolidates those files, cleans up the layout, and gives the query planner something efficient to work with. VACUUM handles the other side of the problem, removing expired snapshots and orphaned files that Iceberg's time-travel mechanism would otherwise hold onto indefinitely. Storage costs drop. Metadata scans get faster. The table stays healthy.
Capricorn energy: "I've scheduled OPTIMIZE to run every night and VACUUM every Sunday. You'll never notice because nothing will ever break."
Independent. Ahead of the curve. Allergic to vendor lock-in.
Aquarius was open source before it was cool. Aquarius believes in freedom of information, interoperability, and building things the community can trust. The revolution will be version-controlled.
Dremio's commitment to open standards is architectural, not cosmetic. Apache Iceberg as the table format means your data is readable by any tool that supports the specification. Apache Polaris, an open-source Iceberg catalog, forms the heart of Dremio's Open Catalog. Apache Arrow as the in-memory format means query results move between systems efficiently. Apache Parquet as the file format is shared across the entire industry. You can run Dremio alongside other Iceberg-compatible tools, migrate to a different query engine if you need to, and read your own data with open-source tooling without negotiating a license. For Aquarius, that isn't a nice-to-have. It's the baseline.
Aquarius energy: "Your data is in open formats, your catalog is open source, and you can leave any time. That's the point."
Dreamy. Intuitive. Dissolves every boundary it finds.
Pisces doesn't wait to be asked. They sense what's needed, flow toward it, and return with something useful before the question has fully formed. An AI agent running against Dremio's agentic lakehouse works exactly the same way: it receives a goal, reasons about what data it needs, queries the lakehouse autonomously, and surfaces an answer without a human writing SQL in between.
This is what Dremio means by the agentic lakehouse. An AI agent is only as useful as the data it can reach, and only as trustworthy as the governance applied to that data. Dremio provides both. In practice, a data team can point an AI agent at Dremio and have it answer questions that would previously have required an analyst to write a query, wait for results, and format a response. The agent handles all of that against live data, with the same access controls that apply to every other user on the platform. Pisces dissolves the boundary between question and answer. Dremio makes sure that when an AI agent does the dissolving, it does so safely.
Pisces energy: "I already queried three tables, joined the results, and drafted the summary. Nobody had to ask me twice."
Whether you're a blazing Aries chasing sub-second query times or a methodical Virgo dissecting execution plans, there's a Dremio feature written in your stars. The lakehouse doesn't play favourites, but the universe clearly does.
If you want to find your match in practice rather than by star sign, you can spin up a free Dremio environment at dremio.com/get-started and see which features you reach for first. The query engine is ready. Mercury is in a neutral position.
Deploy agentic analytics directly on Apache Iceberg data with no pipelines and no added overhead.
By unifying data from diverse sources, simplifying data operations, and providing powerful tools for data management, Dremio stands out as a comprehensive solution for modern data needs. Whether you are a data engineer, business analyst, or data scientist, harnessing the combined power of Dremio and Apache Iceberg will undoubtedly be a valuable asset in your data management toolkit.
We're always looking for ways to better handle and save money on our data. That's why the "data lakehouse" is becoming so popular. It offers a mix of the flexibility of data lakes and the ease of use and performance of data warehouses. The goal? Make data handling easier and cheaper. So, how do we […]
This blog helps you learn about table-driven access policies in Dremio Cloud and Dremio Software v24.1+.
