INSTALL · Binse · V2026.9.16.3
One installer, and one warning box.
Binse is a single Windows installer of 252.2 MB. It goes into your own user folder, so it asks for no administrator rights and writes nothing machine-wide. It is not code signed, so Windows will stop it the first time it runs.
That box is the first thing anybody meets, so it is the second thing on this page rather than a support article found afterwards. The rest is where files go, what an install writes, and how to take it off again with your work intact.
Most of this page is about Windows. Binse for Mac is coming soon and arrives as a disk image instead: it has its own section below. The iPad apps come from the App Store: see iPad.
01 · THE DOWNLOAD
One file, and a hash to check it against.
Setup carries everything Binse runs on: all three canvases, Data Flow, Dashboards and Diagrams, scheduled runs, its own Python runtime, the Node runtime Diagrams renders and exports with, its database drivers, and the shape libraries, icon packs and templates Diagrams draws from. Nothing else has to be installed first, and Setup fetches nothing while it works.
NOT YET PUBLISHED
There is no download link on this page yet, and no hash beside it. Version 2026.9.16.3 is built and measured, and the file is not served for download until the shop opens. When it is, the link and the hash fill the two pending lines in the block of file facts, and the hash is recomputed against the exact binary that is published rather than carried forward from an earlier build.
Check the file before you run it
Open PowerShell in the folder you downloaded to, run the three lines below, and compare the answer to the published sha256 line. Upper case or lower case makes no difference to the comparison. If the two do not match, character for character, delete the file and write to support@binselytics.com.
Get-FileHash ships with Windows. There is nothing to install in order to run it, and it reads the file without running it.
PS> cd "$HOME\Downloads"
PS> Get-FileHash -Algorithm SHA256 `
"Binse*Setup*.exe"
file Binse Setup 2026.9.16.3.exe bytes 252,191,340 size 252.2 MB decimal, 240.5 MiB as Explorer counts it sha256 [not yet published] url [not yet published]
The installer file and the entry in Apps & Features carry the product's name, Binse. The folders it makes still carry the full earlier name, Binse Data Analytics & Dashboards, so that is the name to look for on disk.
02 · THE FIRST RUN
Windows protected your PC.
Those are the words Windows puts on the screen the first time somebody runs Setup. They are not a sign that anything is wrong with the file, and they are not going away until a certificate is bought.
Binse carries no Authenticode signature, and there is no signing step anywhere in its build. Microsoft Defender SmartScreen has no certificate to check, so it warns, and it is right to.
Press More info. Then press Run anyway. Those are the two things to press, in that order. Nothing else on the box moves the install along.
An unsigned installer from a vendor with no download history is exactly what SmartScreen exists to flag, and a habit of pressing through warnings like this one is worth having doubts about. The check open to you instead is the hash in section 01. If it matches, the file on your machine is the file that was published. A code signing certificate would take the box away, and one has not been bought.
+----------------------------------------------------------+ | Windows protected your PC | | | | Microsoft Defender SmartScreen prevented an | | unrecognised app from starting. Running this app | | might put your PC at risk. | | | | More info [ Don't run ]| +----------------------------------------------------------+ press More info, and the box gains two lines and a second button: +----------------------------------------------------------+ | App: Binse Setup 2026.9.16.3.exe | | Publisher: Unknown publisher | | | | [ Run anyway ] [ Don't run ]| +----------------------------------------------------------+
What varies, and what does not
That is a transcription rather than a capture. The middle sentence, and where the buttons sit, differ a little between Windows versions and between languages. The heading, and the two words to press, are what the product's own README tells a customer to expect.
03 · WHAT SETUP WRITES
Per user. No administrator, no service.
Setup asks Windows for the lowest privileges it offers, so there is no elevation prompt and nothing for an IT department to approve in advance. It installs into your own local application data folder, puts a shortcut on the desktop and one in the Start menu, and offers to open Binse when it has finished.
.binsediagram AND .bdx, SO DOUBLE-CLICKING ONE OPENS IT IN DIAGRAMS · PER USER · AN ASSOCIATION YOU SET YOURSELF IS LEFT ALONE · REMOVED BY THE UNINSTALLER
Past the warning box, this is what the shortcut opens: the three canvases, Data Flow, Dashboards and Diagrams, and scheduled runs, on one page, from one install, under one licence. The Binse Enterprise installer adds a card for Explore. The picture was taken on 13 September 2026, before Diagrams joined the home page and the page was laid out again, so it shows the arrangement of that day rather than the one version 2026.9.16.3 opens on. The bar along the bottom counts the database and API connections saved on the machine the picture was taken on, which is the machine every figure on this site was measured on.
04 · WHERE YOUR FILES LIVE
Outside the program folder, with plain names.
Everything you make, and everything the engines derive, sits outside the folder Setup wrote. That is why installing a new version over an old one leaves your work where it is, and why an uninstall can ask before it touches any of it.
Documents is wherever Windows says Documents is on your machine, which is often a folder inside OneDrive. Binse asks Windows rather than assuming.
A password typed into a connection dialog is held in memory for the life of the process and is written to none of these files. Saving a connection string with a plain password in it is refused, with an instruction to use a placeholder or to type the password when you connect.
None of these formats belongs to us. Workflows, dashboards, diagrams and schedules are files with plain names in a folder you already own, and anything Binse writes out is in a format other software reads, CSV, Excel, Parquet and JSON among them, and for a diagram, SVG, PDF and the drawing formats other diagram tools open. A licence that has lapsed reaches into none of them.
Documents\Binse Data Analytics & Dashboards\
Workflows\ saved workflows, and the sample one
Dashboards\ saved dashboards
Diagrams\ saved diagrams, and the sample ones
Libraries\ shape libraries you add or make
Templates\ your own diagram templates
Plugins\ Diagrams plugins you install
Schedules\ saved schedules
Catalogues\ the tables published to Explore
(Enterprise)
Reports\ saved Explore reports (Enterprise)
samples\ the data the sample workflow reads
%LOCALAPPDATA%\Binse Data Analytics & Dashboards\
licence.key a licence file, for the whole app
activation.dat an activated licence key, sealed to this
Windows account
connections.json connections, without their passwords
cache\ Parquet results the engines can rebuild
store\ DuckDB stores for very large files
dashboards-data\ the dashboards registry and its uploads
hub\ the run history, as a CSV
explore\ Explore's settings and scratch files
(Enterprise)
diagrams\ Diagrams' settings and shared palettes,
and the address of a collaboration
relay if one has been set (Enterprise)
diagrams-recovery\ recovery copies of open diagrams
diagrams-ai\ the AI assistant's key, settings and
usage, if it is turned on (Enterprise)
logs\log.txt the engine log
05 · THE RUNTIME AND THE DRIVERS
Both are in the box, and both are most of its weight.
Binse ships the embeddable Python 3.14.7 from python.org inside its own program folder, with every package it needs installed at build time.
Binse runs pip on nobody's machine. Its interpreter is walled off from any Python you already have, so an install cannot change what your own Python does, and your own Python cannot change what Binse does.
Eight optional packages travel with it. Five are database drivers: connectorx, pyodbc, the Snowflake and BigQuery drivers, and the Databricks connector. Three read and write file formats: rasterio, which carries GDAL for the spatial formats, pyreadstat for SAS, SPSS and Stata files, and xlwt for writing the older .xls Excel workbooks. That is why 252.2 MB of download holds 959.2 MB of program files, across 10,806 files, before Python writes its own cache on first run.
Between them, those drivers and the runtime are why 9 kinds of data source work with nothing extra to download. The Data Flow page lists them and carries the receipt that counted them.
A second runtime travels with Setup for Diagrams. Its command line, and the path that renders a diagram to a picture or exports it without the editor open, are JavaScript, so a Node runtime sits beside the Python one in the program folder. It is used by Binse and by nothing else on the machine, it is not added to your PATH, and the scheduled run that refreshes a diagram overnight is what needs it most. Turning a diagram into a PNG or a JPEG still wants a browser, and every supported Windows has one.
WHAT THAT SIZE IS MADE OF
Most of what lands on disk is the runtime and those eight packages rather than Binse itself. The figure counts every program file the build assembled for Setup and nothing in your Documents folder. It was counted in the build folder rather than on a live install of 2026.9.16.3, whose uninstaller and bytecode cache add a little to it.
The trade is deliberate. A smaller download would mean asking a customer to install Python, or a driver, or both, on a machine where they may not be allowed to install anything at all.
06 · UNINSTALLING
It asks one question, and keeps your work by default.
Binse appears in Apps & Features as a per-user entry and is removed from there. No administrator is needed to take it off either.
Uninstalling stops the engine first. Then it removes every scheduled task the product created, because a task pointing at a program that is no longer installed would fail every night for ever.
Derived data goes without being asked about: the caches, the DuckDB stores, the engine log and the recovery copies of diagrams that were open. All of it is rebuilt from your own files on demand, or, in the case of a recovery copy, has no app left to recover into. The saved diagrams themselves are under Documents and follow the answer below, as workflows and dashboards do.
Then it asks one question, in one box, and the answer it suggests is the one that keeps your files. Answering no deletes both folders, including work that Binse never wrote but that you saved beside its own. Nothing asks a second time.
An uninstall run silently, without the box, keeps them. Installing a new version over an old one never asks that question and touches none of it, because none of it is in the program folder.
Keep your workflows, dashboards, diagrams, schedules,
catalogues, reports, registered data and licence?
Yes keeps them (under Documents and Local AppData) for a
future install.
No deletes them as well.
Either way, nothing of this program will run on a schedule
again.
[ Yes ] [ No ]
07 · WINDOWS REQUIREMENTS
Windows, 64-bit. That is as precise as this page gets.
The installer refuses anything below Windows 10 and installs in 64-bit mode only. Those are two lines in an installer script rather than a test result, and a line in a script is not a machine anybody has installed on.
The minimum Windows build is confirmed on a clean machine before the first release, and this page carries it the day it is.
08 · WHAT THIS INSTALL DOES NOT DO
The reasons an IT department might say no.
Same typeface, same size, same page as the rest of it. If one of these is a dealbreaker, better to meet it now than on day three. The price page carries the commercial ones.
The installer is not code signed
Everybody who installs Binse meets a SmartScreen warning and has to press through it. Some managed machines will not allow that at all. A certificate is the fix, and it has not been bought.
One machine, one Windows build
The product has been installed on a single laptop, and the minimum Windows version is a line in a script rather than something anybody has tried.
There is no MSI and no managed deployment
Setup is a per-user executable that the person who will use Binse runs themselves. There is no MSI package, no Group Policy deployment and no rehearsed unattended install, so putting Binse on a floor of desks means asking each person at each desk to run it.
Binse does not look for updates
Nothing in the product asks the internet whether a newer version exists. That is deliberate, and it has a cost: a new version means coming back to this page and running Setup again over the old one.
Windows and Mac, and nothing else
Binse for Mac is coming soon, and the section below describes it. There is no Linux build and none is planned.
The engine listens on the loopback address
Binse runs one local process on 127.0.0.1:8767, and anything else running as you on that machine can reach it. That is a trade a single-user desktop product makes, and it is written down here rather than described as a security feature.
09 · ON A MAC · Coming soon
Binse for Mac: the same three canvases.
Binse for Mac is the desktop app, not a cut-down version. Build a workflow in Data Flow, design the dashboard, draw the diagram and set the workflow to run on its own, all on your own Mac, with your data never leaving it.
It feels like a Mac app
⌘ where Windows has Ctrl, and the labels say so. File, Edit and Go menus, the macOS print sheet, and each workspace's user guide one keystroke away.
Your work in your own folders
Workflows, dashboards and diagrams are ordinary files in a Binse folder in Documents, with the samples copied there on the first start.
Scheduled runs, the Mac way
A saved workflow runs on its own through a login item that macOS asks you to allow once. As on Windows, it runs while you are signed in.
- Runs on
- macOS 14 or later, on Apple Silicon
- Any Mac with an Apple M-series chip.
- How it arrives
- A disk image from this site
- Signed and notarised by Apple, so it opens without a warning. Drag Binse into Applications.
- What it costs
- €99 per user, a year
- VAT included. The same price as on Windows, as its own licence: see the price page.
- Databases
- The same sources as Windows
- SQL Server connects with a SQL Server login over an encrypted connection. Access tables are read; writing to Access needs Windows.
- Edition
- Binse
- Binse Enterprise is for Windows.