FAQ
We bias toward limitations you will hit in week three, not glossy promises. If something is missing, say so in the contact form—docs issues get triaged like product bugs.
Getting access
Do you ship an on-prem edition?
Select modules support VPC bundles with weekly refresh cadence. Air-gapped sites require manual artifact drops—we do not stream from disconnected vaults.
How long does connector certification take?
Most read-only warehouse paths land in six to nine weeks if schemas stay stable. Drift in upstream column names adds review cycles.
Documentation
Can we fork your doc templates?
Yes, under the workspace license. Attribution footer text should remain visible unless your counsel advises otherwise.
Why are some tutorials marked “staging only”?
Those flows touch mutable sandboxes. Running them against production keys is unsupported and will void goodwill support.
Support posture
Do you guarantee same-day fixes?
No. Severity-based targets exist, but we do not promise instantaneous remediation—especially across holiday windows in Korea.
What is explicitly not included in base support?
Custom data science model training, legal interpretation of your policies, and hands-on keyboard work inside your vendor consoles unless a statement of work says otherwise.
Limitations we want on the record
Will the playground run arbitrary network calls?
No. The browser sandbox blocks outbound fetches so workshops stay predictable. Use your own staging tenant for live calls.
Does the portfolio grid replace workshop facilitation?
Absolutely not. Software captures annotations; humans still facilitate the conversation. If facilitation is missing, adoption plateaus.