Arkush for organizations
Arkush for organizations is Arkush set up for one organization: its warehouse, its people and its rules. The canvas, the charts and your agent work as they do here. What needs an organization behind it turns on: queries the server runs on a schedule, sharing with your colleagues, and dashboards that arrive in Slack.
Your warehouse
Here, a BigQuery query runs in your browser under your own Google account, and only when someone presses Refresh. In an organization, the server runs it.
The server runs your SQL as a service account the organization grants in Google Cloud. No dashboard depends on one person's login, and a dashboard keeps working while its author is on holiday.
Set a schedule, and warehouse queries, Google Sheets and files at an address refresh on their own. Everyone who opens the dashboard reads this morning's numbers, and nobody presses Refresh.
Run SQL on the organization's PostgreSQL databases on Cloud SQL, beside BigQuery. The server reads private Google Sheets and files at an address, and keeps them fresh too.
Your people
Here, a dashboard is private or published to the internet. In an organization, it goes to exactly the people who need it.
Give a colleague view or edit access, share with a whole team as a group, or open a dashboard to everyone in the organization. Your colleagues sign in with their work accounts.
A colleague who can read a dashboard adds charts of their own beside it, over the same data, without touching yours. When a chart is good, an editor adopts it into the dashboard.
Analysts share datasources everyone reuses, keep the team's themes and fonts, and mark the dashboards the organization stands behind as official.
Delivery
Schedule a dashboard's charts and tables into a team's channel: the weekly numbers land on Monday morning, where the team already talks about them.
Each colleague picks the charts they care about and a time, and gets them in their own Slack direct messages.
Your agent
Your agent browses the warehouse catalog — datasets, tables, columns and their descriptions — and picks the table itself. The catalog shows names and descriptions, never rows.
Your agent runs the queries on the server, as the service account the datasource names, and checks the result. You don't press Refresh for it.
Analysts write down the organization's tables, terms and house rules once, and every agent reads them before it builds a dashboard.
Arkush for organizations runs on the organization's own server, and the data stays there. Warehouse access is read-only, readers never run a query, and an agent never gets more access than the person who connected it.
Waitlist
Join the waitlist with the account you use here. If you like, tell us about your team and what you would use Arkush for.
We keep your email address, the date you joined, the features that brought you here, and what you write. You can leave the waitlist on this page at any time, and we remove an entry after 12 months.