What does Dynepta actually do?
We set up a data warehouse for your business on Google BigQuery, connect it to your systems, and run it for you. You end up with one checked, up-to-date place for your company’s numbers, ready for dashboards, spreadsheets or AI tools.
What does it cost?
There are two parts: a once-off setup project, quoted after our first conversation once we know your systems, and a monthly retainer for running it. Google bills you directly for your cloud usage, with budget alerts and query limits in place. Dashboards are quoted separately.
What do we need to have in place?
A Google Cloud organisation on your own billing account, and Google Workspace, since sign-in, access groups and alerts in Google Chat all build on it. If you don’t have these yet, we’ll help you set them up as part of onboarding.
Will this slow down or change our live systems?
No. Changes are read from your database’s own change log by a read-only user, so your staff won’t notice it. Your database administrator turns that log on once, and we give them the steps. Exports can come from a copy of your database instead. Running and tuning your operational systems stays with your IT team or software vendor.
How will we know it’s working?
Your team gets a console that shows every source, quality gate, run and cost, and the lineage of every table. Problems post to a Google Chat space with the steps to fix them, serious ones go by email too, and a daily summary says what ran. Everything the console shows is also in BigQuery and the Google Cloud console, so nothing depends on it.
Where is our data stored?
In your own Google Cloud projects. Our standard region is europe-west1 in Belgium, because Google’s service for live database feeds isn’t offered in any African region. Keeping personal information outside South Africa has POPIA implications, so we go through what that means for your business, and how our data processing agreement covers it, before anything is built.
How do you handle POPIA?
You remain the responsible party and Dynepta acts as your operator, processing data only on your written instructions. Personal columns (PII) are tagged when they arrive, then masked or hidden for anyone without a reason to see them. Access is granted to groups, never to individuals, and every read is logged in a register your information officer can export.
Can it grow with us?
Yes. BigQuery handles large volumes without any servers for you to size or upgrade. Adding a source, a team or a new set of tables follows the same steps every time, so the platform grows without being rebuilt.
How quickly do you respond when something breaks?
Alerts reach us automatically. A critical problem, such as a stopped pipeline, gets a response within 4 business hours, and anything else by the next business day. Because a failed check holds back the steps after it, bad data doesn’t reach your reports while it waits.
Can we use AI assistants like Claude on our data?
Yes. AI assistants connect over MCP (the Model Context Protocol) and work the way your team does in the console: they find tables, read definitions and run read-only queries, as the person using them. Personal and restricted columns are never sent to the AI, each query has a cost limit, and an assistant can only propose a change, which then waits for a person to approve it.
Do you build dashboards?
Yes, as a separately priced service, usually in Looker Studio. Because each figure is defined once, every dashboard shows the same numbers.
What happens if we stop working with you?
You keep your data and the environment built for you. We remove all of our access, hand over documentation, and stop receiving check results. The code we use to build and run platforms stays ours.
Still have a question?
Tell us about your systems and reporting needs. We reply within one business day.