CHANGELOG · Binse
Every release, with the day it shipped.
Nine releases of Binse carry a version number. The work before them was done on two separate products, and none of it has a version number of this one, so none is invented here. The last section lists the faults that are open today.
Every version below installs into folders still named Binse Data Analytics & Dashboards, and each entry uses the names of its own day. The product is now sold as Binse, with Data Flow, Dashboards, Diagrams and scheduled runs, and Explore belongs to Binse Enterprise, which is in development.
01 · CURRENT VERSION
2026.9.16.3
Dated 2026-09-16, the day its installer was built. The tool and visual counts on this site, and every figure about Diagrams, were measured against it that day.
Diagrams hands work to the other two canvases
Dashboards gained a diagram visual. Choose a saved diagram, point a column at its shapes and a measure at them, and the drawing colours, labels and badges itself from the data like any other visual, with the same rules and the same legend it would have in Diagrams. Clicking a shape cross-filters the page. The drawing is taken once and kept inside the dashboard, so a dashboard exported as one file still draws it on a machine with nothing running, which is the state most dashboards are opened in.
Data Flow gained Send to Diagrams, beside the run chip, and Diagrams gained Send to Dashboards. Data Flow offers the workflow drawn as lineage, the last run drawn step by step with rows and durations on the wires, or the diagram a step already feeds, and a tool of the same name does it inside a workflow that nobody is watching. Both directions go through a small file rather than a message, so the hand-off survives a fresh window, tomorrow and an unattended run. With Diagrams not installed, the button explains itself instead of failing.
Scheduled runs can refresh and deliver a diagram: open it, read its data sources again, write the rows into the shapes bound to them, run the rules again so the drawing recolours, recompute the charts inside it, save it and send it out, with no browser and no window open. A workflow that writes a file in step one, and a diagram bound to that file in step two, is the whole pattern. The single-file web page, SVG and PDF are delivered that way. The picture formats need a browser, so a schedule that asks for one is refused when it is saved, with the reason, rather than failing in the middle of the night.
The home page was laid out again around the third canvas: Data Flow, Dashboards and Diagrams as cards across the top, Schedules and Connections as two bars under them, and what you last worked on below that, each file opening in the tool that made it. Binse Enterprise keeps its four tools with the same two bars in a column beside them.
Fixed in the same build, all of it in the new diagram visual: the drawing brought its own white page with it into the card, the ink was fixed to the light theme so a dark dashboard got a light drawing, and the card now measures the real drawing and fits it, with zoom and pan. The contrast check found a real defect while that was being done, dark text on a mid-amber rule fill that nobody could read, so text over a rule-coloured shape now takes a readable ink. Connector labels on generated diagrams collided because the layout left them nowhere to go, and the layout now sizes each label and hands it over with the shape.
The installer is 252.2 MB. This build was made for Binse only: there is no Enterprise installer of this version and no relay beside it.
02 · PRIOR VERSIONS
What came before it.
Eight earlier versions, each named after the day it was built. Below them, the period the repository does not reach.
Hover tips everywhere, and the Diagrams user guide
Every control in Diagrams that is not self-evident now explains itself on hover and on keyboard focus, the Enterprise dialogs, the settings, the data wizards, the collaboration panels and the assistant among them. A new setting or a new toggle fails the type check until somebody writes its tip, so the coverage cannot quietly rot. Widening that check found a real defect: the tooltip layer was overwriting the description a screen reader reads, which lost it on the encryption switch and on the import mapper's fields, and it now adds to that description and puts it back.
Diagrams gained a user guide of its own, which brings the product to 5 of them. It is built rather than typed: every table in it, the shape libraries and their counts, the templates, the layouts, the import and export formats, the accessibility checks and the whole keyboard, is generated from the code, and the build stops when a shortcut or a check has no sentence beside it. F1 opens it inside the app, and the same words are a chapter of the combined guide.
Also in this build: one button that collapses or expands every category of the shape palette at once, and the wordmark in the product's own colour.
Diagrams ships inside Binse
A third canvas, in both editions, from the same installer and under the same licence: flowcharts and org charts, network and cloud maps, floor plans, mind maps, BPMN processes and a whiteboard. It carries 74 shape libraries holding 6,161 shapes, 111,893 icons in 1,045 packs, and 98 templates in 24 categories. It reads 38 file formats and writes 32, lays a diagram out 19 ways, and draws 13 kinds of chart inside a diagram.
In the app it is the fifth workspace, beside Data Flow, Dashboards, Explore and Schedules, on the same home page and behind the same licence. Diagram files are associated with it for your Windows account, so double-clicking one opens it. An unlicensed computer is given a page that sends it to the licence screen rather than an editor that would have worked without one.
What Binse Enterprise adds is inside Diagrams rather than beside it: live collaboration, comments, version history and an AI assistant. The collaboration relay is a service one machine in an organisation runs, so it ships as a zip of its own beside the Enterprise installer instead of being installed on every desk.
The installer grew for all of that. It now also carries a Node runtime, which the Diagrams command line and its render and export path need, and the shape libraries, the icon packs, the templates and the fonts.
Two editions, Binse and Binse Enterprise
One code base became two installers. Binse is what is sold: Data Flow, Dashboards and scheduled runs. Binse Enterprise, in development and not on sale, adds Explore. Each installer carries its edition's name on the file, the shortcuts, the Apps & Features entry, the window titles, the home page and the licence screens. The product's own name, Binse Data Analytics & Dashboards, is unchanged in the program folder, the Documents folder and the licence.
Explore needs an Enterprise licence rather than only the Enterprise installer, because the edition is written inside the signed licence. Installing Enterprise over Binse adds Explore. Installing Binse over Enterprise removes Explore's files and leaves your catalogues and reports in Documents, because they are yours.
Scheduled runs are a feature of both editions rather than something either one adds.
A licence key, and 51 file formats
The licence screen in Data Flow and Dashboards has one box, labelled Licence key. It takes a Lemon Squeezy licence key, which the app activates with Lemon Squeezy directly and confirms in the background about once a week, or a key from the key bank, which the activation service exchanges for a signed licence lasting 35 days that renews itself. Release this computer is on the licence screen, in both workspace footers and on the home page. The computer code is now made from the Windows machine identifier alone, so renaming a PC or changing Windows account no longer reads as a new computer, and a licence file issued against the older code still works. The route that sends a computer code for a licence file issued by hand is still there, folded under the box.
That closes the known issue found on 2026-09-11 that nothing could move a licence's end date. A key-bank licence is now a lease of 35 days, so a refund or a cancellation takes effect within one lease, and the activation service gained the call that moves an order's end date.
Data Flow reads 51 file formats and writes 35 of them, from one registry that Input Data, Output Data, the results pane's Export and the file browser all read: text and XML, spreadsheets, Parquet and its relatives, QlikView QVX, databases kept in a file, SAS, SPSS and Stata, the common spatial formats and grids, and zip, gzip, bzip2, xz and tar archives. The installer carries three new packages for them, rasterio, pyreadstat and xlwt, and three small readers, and it grew to 252.2 MB. The Data Flow user guide was rewritten for the new licence screen and carries the full format table.
The workspace that was called Data Analytics is now called Data Flow, in the app, in its user guide and on this site. The home page sets the four workspaces out two by two, in the order Data Flow, Dashboards, Explore and Schedules. The product's own name, Binse Data Analytics & Dashboards, is unchanged.
Found and fixed on the same day, 2026-09-13: the first build of this version
bundled a copy of the Access reader package without the method the reader calls, so reading
an Access table on a computer without Microsoft's Access Database Engine failed the product's
own test for .accdb and .mdb. The installer was rebuilt with a newer
copy of that package and the test passes. It was listed below as a known issue until then.
Writing an Access file, or running SQL inside one, still needs Microsoft's driver.
The honest part of this entry: none of it is committed to the repository
yet, and the version constant in the shell went from 2026.9.10 straight to
2026.9.13. No installer numbered in between is on the build machine, and none is
listed here.
All four workspaces, one installer
Data Flow, Dashboards, Explore and Schedules are in one installer and answer on one local port. The installer now creates the Catalogues and Reports folders that Explore writes into, and the uninstaller removes every scheduled task the product created, so a task can never be left pointing at a program that is gone.
The formula language moved out of the Data Flow engine and into the shared core, which is why Data Flow and Explore now run the same 76 functions rather than two copies of them. The Dashboards designer keeps its own separate formula box, which is a different implementation with a different function list. The user guides were regenerated on 2026-09-10.
This is the version the benchmark, export and install measurements on this site were taken against, on 11 September 2026. The repository holds this release and the one before it as a single change set that has not been committed. The line between the two is drawn by the build notes and by the version constant in the shell, not by a commit.
Schedules and Explore
The third and fourth workspaces were added to the installer. Schedules runs saved flows and dashboards unattended through the Windows Task Scheduler that is already on the machine. Explore is a field picker over published tables: it compiles to the dialect of the backend each table lives in, runs as the signed-in person, and saves reports as its read-only half. A catalogue file decides what is published.
The installer gained a fifth compiled module, a copy of Explore's web build and a sample catalogue. It needed no new runtime dependencies. BigQuery access moved onto the ADBC driver directly, because Polars could not hand that driver its options, and going direct is also what gives Explore its dry run and its billed-bytes cap.
The palette more than doubles
Data Flow reached 110 tools in 12 categories. Seven of those categories did not exist the day before, among them Developer, Interface, Investigation and Time Series. The new categories were given their own colours in the palette.
Two smaller fixes shipped with it: a licence refusal is never served from the cache, and a column type in the dashboard grid was widened to match what the code already did.
Two products become one
Data Flow and Dashboards became one product: one installer, one process on one port, one licence file, and a home page that opens either. The install is per user and asks for no administrator rights. The canvas gained tool containers, macros that expand into the parent flow before a run, and parameters that a saved flow declares and asks for before it starts.
This is also the day the repository was created. Everything from here on can be read commit by commit. Nothing before it can.
Before 2026-09-07, no version number exists
Data Flow and Dashboards were built as separate products and neither carried a version number of the merged one. Their own build notes are dated: a working dashboard designer with intake, cross-filtering and single-file export on 2026-09-04; 362 visual types across 17 categories on 2026-09-05; and on 2026-09-06 the large-file path, a Parquet store read through DuckDB, cubes for interaction, and exports that carry cubes instead of rows.
None of that work is given a version number here, because none of it has one, and the repository does not reach back to it.
ONE THING THE VERSION NUMBERS DO NOT DO
The shell's own version constant read 2026.9.7 until it was set to
2026.9.10. The two releases in between were named in the build notes and in the
Explore module, but the shell was not renumbered for either of them. So a copy of
2026.9.8 or 2026.9.9 reports the older number from inside the
application. It is a bookkeeping fault rather than a functional one, and it is written here
because a changelog that hides its own bookkeeping is not worth reading.
03 · KNOWN ISSUES, DATED
What is wrong with it today.
Set in the same typeface, at the same size, on the same page as the releases. Each entry carries the day it was found. An entry leaves this list when the fix ships, and it keeps its dates when it goes.
An exported dashboard still polls the host it came from
An exported dashboard carries the application shell's heartbeat. It asks
whatever served it for /api/ping every five seconds, and for
/api/workspaces once. Both fail harmlessly against anything that is not the
Binse engine, and the dashboard renders in full either way. It contacts no third party and
no host except the one the file was opened from. The poll is dead code in the viewer build
and has not been taken out of it.
Two workspace pages fetch a web font from an outside host
The home page loads a stylesheet from
fonts.googleapis.com. The Data Flow canvas loads the same stylesheet and
then a font file from fonts.gstatic.com. Dashboards, Diagrams, Explore and
Schedules ask for nothing outside the machine, and Diagrams carries its own typefaces in
the installer. This is a request to a third party in a product sold on
the promise that it stays on your machine, and it happens on the first screen, before
anybody has done anything. The fix is to self-host both typefaces, which is what this
website does.
Scheduled tasks are filed under an internal name
Every Windows scheduled task the product creates goes into a Task
Scheduler folder called Binse Hub. Hub is the internal name for the part of the
app that the product and the installer call Schedules and this site calls scheduled runs. The tasks themselves run
correctly. Anyone who opens Task Scheduler sees a name nothing else uses.
The combined user guide leaves out Schedules and Explore
The generated guide has chapters for Data Flow, Dashboards and, since 2026-09-16, Diagrams. Schedules and Explore each have a guide of their own, and neither is in the combined document, so the combined document understates what is installed. Writing the two missing chapters is the fix.
Explore has not met a live warehouse
This concerns Explore, part of Binse Enterprise. Explore's warehouse SQL is checked as text, and its driver options are checked without connecting. That covers what fails silently. It is not the same as one real table, one real query and one real bill, and that run has not happened. Until it does, treat Explore over a live warehouse as unproven rather than proven.
The installer is not code signed
Windows shows a SmartScreen warning the first time the installer runs, because the file carries no publisher signature. The install page shows that screen and says which buttons to press. Signing it is a cost and a decision, and neither has been taken.
A key from any Lemon Squeezy store would be accepted
The app checks a Lemon Squeezy licence key against a store and a product, and in 2026.9.16.3 both are empty, because the store has not been set up. Until they are set, the app accepts a valid key from any Lemon Squeezy store and writes a warning to its log. Setting them is a step before the first sale.
WHAT IS NOT ON THIS LIST
These are faults. The permanent limits of the product, the things that are not going to change because they are the shape of it, are listed on the home page under what it does not do. If you find something on this page that is wrong, write to corrections@binselytics.com and it will be corrected and dated.