Start with the database.
Bring PostgreSQL, MySQL, and compatible engines into the analytical workflow.
Clone PostgreSQL, MySQL, and compatible databases into FastBI Lake. Keep your application serving customers while analysis runs against the copy.
customersordersorder_itemsServes the application
customersordersorder_itemsServes scans, joins, and reports
Use a recurring cadence for periodic analysis. The Lake copy reflects the last completed refresh.
Move heavy reporting to Lake. Keep your application database focused on the next customer.
SELECT customer_id, SUM(total)
FROM orders
GROUP BY customer_id;Illustrates the goal for scan-heavy reporting, not measured query times. Actual performance depends on data, indexes, query design, and compute; Lake is not faster for every query.
01Make a copy
Your operational tables already hold valuable answers. Replicate brings a copy into Lake so you can investigate across customers, orders, and years of history.
Bring PostgreSQL, MySQL, and compatible engines into the analytical workflow.
Give analysis its own dataset to scan and join.
Run analytical queries against the Lake copy rather than the application tables.
02Keep it current
A daily business review and an operational dashboard don't always need the same update cadence. Scheduled and continuous replication serve different needs.
Refresh on a cadence suited to periodic reporting.
Follow database changes for analysis that needs fresher data.
Compatibility depends on the engine, version, permissions, and replication features available.
03Analyze the copy
Once the data is in Lake, explore it with SQL, combine it with other datasets, and build intermediate tables for repeated analysis.
Copy source tables into Lake.
Give scans and joins an analytical home.
Explore, prepare, and report on the copy.
Scheduled $5/database/mo · Continuous $15/database/mo, plus excess CDC (planned).
View full pricing →Join the waitlist for early access.