Your lakehouse server runs four pieces that work together: MinIO stores the files, Apache Iceberg organizes them into proper tables, DuckDB runs the queries, and Grafana shows the results. You do not need to memorize how they fit together, because the vibe-code agent in your Open WebUI chat already knows the layout. It can read the configuration, write SQL, run commands, and restart services. Here are ten everyday jobs you can simply hand over.

1. Ask questions in plain English

The fastest way to get value from the stack is to type a question and let the agent do the rest. It checks the schema in the Iceberg catalog, writes DuckDB SQL that reads the Parquet files straight from MinIO over the S3 API, runs it, and shows you a small table or chart instead of a wall of SQL. When the first answer raises a follow-up, you ask it right there and the agent adjusts the query. This is the job that replaces half your spreadsheet work. Try: “What were our top 10 customers by total order value last quarter, broken down month by month?”

2. Turn a spreadsheet into an Iceberg table

CSV exports rot in download folders, and nobody remembers which file was final. Point the agent at a file on the server or drop one into the chat, and it will upload it to MinIO, infer the schema, create a real Iceberg table in the catalog, and show you a preview of the first rows. From then on the data is versioned, partitioned, and queryable next to everything else, instead of living outside the system. Try: “Take this CSV of March expenses and turn it into an Iceberg table called expenses_2026_03.”

3. Build a Grafana dashboard

Describing the chart you want is enough. The agent writes the dashboard JSON, points the panels at the right queries, sets time ranges and refresh intervals that make sense, and saves everything to a proper folder. You then iterate by talking: make the revenue line thicker, add a breakdown by country, move a panel up. Nobody has to learn the panel editor before they can see their own numbers. Try: “Make me a sales dashboard with daily revenue, order count, and average order value, split by country.”

4. Create a bucket and lock it down

New projects need new storage, and the defaults matter more than most people think. The agent creates the bucket in MinIO, confirms public access is off, writes a policy so only the lakehouse service account can read it, and wires the credentials into the query setup so DuckDB still works. It then shows you the policy it wrote, in plain language, so you can verify it. No more “temp” buckets that turn out to be open to the world. Try: “Create a private bucket called finance-reports and make sure only the lakehouse service account can read it.”

5. Back up a table before a risky change

Iceberg makes snapshots cheap, but a snapshot only helps if it exists before something goes wrong. Before you run a cleanup script or a mass update, ask the agent to snapshot the table and, for extra safety, copy it to a separate backup bucket in MinIO. It verifies the copy by counting rows on both sides and tells you the numbers match. That two-minute check is the difference between a bad afternoon and a bad week. Try: “Back up the orders table to the backup bucket before I run my cleanup script, and confirm the row counts match.”

6. Clean up old snapshots and orphan files

Every write to an Iceberg table leaves snapshots and files behind, and storage quietly grows while the queries stay the same. The agent can expire snapshots older than a threshold you choose, remove files that no table references anymore, and report exactly how much disk came back. It is careful to keep the snapshots you still might need, and it shows the list before deleting anything. Run it monthly, or ask when a bucket looks bloated. Try: “Expire snapshots older than 7 days on all tables and tell me how much space we got back.”

7. Fix a service that stopped

Grafana shows a blank page, or queries fail, and you do not know which of the four pieces is at fault. The agent checks container status, reads the logs, finds the failing service, and restarts just that one. It tells you what it found instead of leaving you to guess, and it checks again a few minutes later to confirm the fix held. You stay informed without learning the whole compose file. Try: “Grafana is showing a blank page — check the logs, find the problem, and restart whatever is stuck.”

8. Export results and share a link

Sometimes a colleague just needs a file, not a dashboard login. The agent runs the query, exports the result as CSV or Parquet into MinIO, and creates a presigned URL that expires when you say so. That beats emailing attachments around, and it beats handing out permanent credentials for a one-off request. The link works with any browser, and the file stays on your server the whole time. Try: “Export last month’s order lines as CSV and give me a download link that stops working after 24 hours.”

9. Add a column without breaking anything

Iceberg supports schema evolution, so you can add or rename columns in place instead of rebuilding tables and replaying history. The agent alters the table, backfills the new column from existing data or a lookup file you provide, and verifies your old queries still run against it. The change lands in the table’s history, so it can be reviewed later. Try: “Add a region column to the customers table and fill it in from the country column using the mapping in countries.csv.”

10. Look at the past with time travel

Iceberg keeps every snapshot, so you can query a table exactly as it stood last Tuesday at 6 pm. That settles “who changed this?” arguments, lets you reproduce last month’s report exactly, and lets you fish back rows that were deleted by accident. No restore, no backup tape, just a query with an as-of clause over the same storage. Try: “Show me what the inventory table looked like yesterday at 6 pm and list every row that changed since then.”

See it in action

Official walkthroughs from the MinIO and DuckDB teams:

Worth a watch next:

• The Key Components and Technologies Essential for a Data Lakehouse — a tour of exactly the four pieces this stack combines: object storage, the Iceberg table format, a query engine, and dashboards.
• DuckCon #7 – Making Iceberg walk and talk like Postgres (Marco Slot) — querying Iceberg tables through a Postgres-compatible layer pairs naturally with asking questions in plain English.

Pick one job from this list and try it today — the agent shows its work as it goes, so you can always ask why it did something. To run this stack on your own private server, see Data Lakehouse (Iceberg + MinIO + DuckDB + Grafana) on OpenSysLab.