Item logo image for Zoost - workbench for Zoho Analytics

Zoost - workbench for Zoho Analytics

ExtensionDeveloper Tools5 users
Item media 5 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 1 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 2 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 3 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 4 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 5 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 1 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 1 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 2 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 3 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 4 (screenshot) for Zoost - workbench for Zoho Analytics
Item media 5 (screenshot) for Zoost - workbench for Zoho Analytics

Overview

Independent, unofficial: mirror a Zoho Analytics workspace to local files - views, columns, foreign keys, query-table SQL.

Zoost mirrors a Zoho Analytics workspace into plain local files, then draws you the map that Zoho Analytics never shows you. A workspace that has been alive for a few years is hundreds of views. Some are tables, some are query tables with SQL somebody wrote at 2am, most are reports built on top of reports. Zoho Analytics will tell you what a single view depends on if you ask it, one view at a time. It will not tell you the shape of the whole thing, it will not tell you what changed last month, and it will not tell you which of those hundreds of views nothing reads any more. WHAT IT DOES - Judge it before you give it access to anything. "+ Sample" writes a workspace of invented data into your working folder - tables with their columns and foreign keys, query tables with their SQL, reports and dashboards - so you can open the census, the ER diagram, the lineage and the exports without a Zoho Analytics tab and without an account. It is generated, never fetched, everything that would talk to the platform is disabled for it, and it is deleted like any other workspace. - Local mirror, your Git. One pull writes the whole workspace to disk: the view census, the column structure of every table and query table, the relations, and one .sql file per query table. Zoho Analytics keeps no history of anything: change a query table's SQL, a column or a relation and the previous state is gone. Commit the mirror and git diff answers "what changed in this workspace last month". - Every view, in one list. All of them with type, folder, owner, column count and dates, filtered by type and searched by name, folder or column name. Search a column name to find which tables carry it, before you go looking for where the data lives. - The structure of anything, including reports. Tables and query tables carry their own columns with Zoho's data types. A report or a pivot has none of its own - so Zoost follows what it is built on and shows you that structure instead, saying whose it is rather than pretending it is the report's. - Foreign keys on every column, and they are links. Each column shows what it points at and what points at it, both directions, because a foreign key is not symmetric. Click one and you are looking at the other table. Taken from the ER model Zoho Analytics itself draws, with the join written exactly as Zoho writes it. - ER diagram that stays readable. Tables as boxes, relations as arrows, the join on the arc. Focus one table, adjust the depth, walk the graph by clicking. Click an arc to isolate one relation and fade the rest. Boxes can be dragged: the automatic layout is a starting point, and what you arrange is what the PDF prints. Live sliders for spacing, spread, label gap and label size, and Save PDF for wall-size prints. - The SQL of your query tables. Read in the panel, written to disk one file each, and searched across all of them at once - the "in: SQL" switch beside the search box looks inside every query in the workspace, literally or as a regular expression (with named patterns you save and manage yourself), and shows, per query, the first matching line and how many times the pattern occurs. Each one also records which source tables it reads and which of their columns it actually involves. - What nothing depends on. Ask Zoho Analytics its own dependency question for every view, and see which ones nothing in the workspace reads. Stated as candidates, never as a verdict: a shared link, a scheduled export, an embedded report or an API consumer is invisible to that graph, and Zoost says so next to the number. - Design and data, told apart. Zoho Analytics tracks when a view's design last changed separately from when its data last refreshed. A report whose data refreshed nightly for two years but whose design nobody has touched since 2019 is a very different object from one redesigned last week, and the list shows both. - What Zoho put there, and what you built. The ER model flags system tables - the ones synced from a connected source rather than built by you. The view list marks them; the health view counts them. - Health audit. Views nothing depends on, tables in no relation at all, views with no description, items that could not be read. Counts and lists, with no thresholds and no score, and every figure stating what it does not cover. - Exports you can hand over. The whole workspace as one self-contained HTML file, or as Markdown shaped as context for an external AI tool - the Markdown carries the constraints of Zoho Analytics' own SQL dialect too, so an assistant that has never seen Zoho Analytics does not write queries that cannot run. A dialog decides section by section what the file may contain; the SQL is opt-in and flagged every time. - Optional AI assistant, bring your own key. Anthropic (Claude) or OpenAI (ChatGPT). With Anthropic it runs as an agent with read-only tools over your local mirror - it can read a structure, follow a foreign key, open a query's SQL, search columns, and say what depends on what. It is told what Zoho documents about query-table SQL, so what it writes is a draft you can paste rather than plausible SQL that will not run. - Your key, your machine, your choice. The API key is stored locally and sent only to the provider you pick. You can protect it with a passphrase you choose - it is then stored encrypted and asked for once per browser session. Off by default, because on a personal machine it buys little and on a shared one a lot, and the trade-off is explained where the choice is made. - Built for more than one workspace. The workspace does not have to be yours: one working folder holds a subfolder per workspace, each bound to the one it came from, so a consultant can keep every client mirrored at the same time. The panel takes the workspace from the tab you are on, so which client you are looking at is answered by the browser rather than by remembering. WHO IT'S FOR Zoho Analytics builders, data analysts and consultants who need to understand a workspace rather than only use it: what a report is built on, which tables a query reads, what nothing depends on any more, and what changed since last month. WHAT IT DOES NOT DO - It calls no endpoint that creates, edits or deletes anything in Zoho Analytics. One call is a POST whose URL contains CREATE - ZDBCreateERD.ma, which returns the workspace ER model and is the call the Zoho Analytics diagram screen itself makes. What can be said from a browser is what Zoost sends; it is named here because anyone checking the read-only claim literally will find it. No creating, editing or deleting a view, ever. - It never reads the rows in your tables. Structure, relations, SQL and metadata only. The endpoints that return cell values exist and are deliberately not called. - It does not run, validate or deploy SQL. Whatever the assistant writes is a draft; Zoho Analytics is the only thing that can tell you it compiles. - Report definitions - which columns a chart puts on which axis, and how it aggregates them - are not covered. The endpoint that carries them also carries the computed series, which is your data. - Lookups between base tables come from Zoho Analytics' own ER model. What that model does not draw, Zoost does not know. HOW IT WORKS Everything happens in your browser, using the Zoho session you are already signed into. There is no server, no account and no telemetry. The mirror is written to a folder you pick with the browser's own folder picker. Two things can leave your machine, both only when you make them: what you send to an AI provider, if you choose to configure one, and a problem report you have read in full and pressed Send on. Never the rows in your tables, because Zoost does not read them. DOCUMENTATION AND PRIVACY Source code: https://github.com/ivannot/zoost Guide: https://zoost.it/docs-analytics Privacy policy: https://zoost.it/privacy Home: https://zoost.it When something fails, the panel can build a problem report - versions, the error, the last few status lines and counters - open it on a page on zoost.it with the text already in it, where you read it, trim it if you want, and send it - or not. It becomes a public issue only when you press send. It carries no SQL and no key at all; names, paths and ids are stripped wherever they can be recognised - which is why you are shown the whole text first. Nothing is ever sent automatically. Free and open source, Apache-2.0. Maintained in spare time on a best-effort basis; there is no guaranteed support or response time. Independent and unofficial: not affiliated with, endorsed by or sponsored by Zoho Corporation.

Details

  • Version
    1.31.0
  • Updated
    September 6, 2026
  • Size
    272KiB
  • Languages
    English
  • Developer
    Website
    Email
    ivan@zoost.it
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization
The developer has disclosed that it will not collect or use your data. To learn more, see the developer’s privacy policy.

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes
Google apps