%20or%20the%20dark%20window%20chrome.%20Any%20surface%20that%20needs%20it%20in%20another%20colour%20uses%20the%20file%20as%20a%20CSS%20mask%20and%20paints%20it%20with%20a%20token,%20rather%20than%20a%20second%20copy%20of%20the%20geometry%20in%20another%20colour.%20--%3e%3csvg%20viewBox='0%200%20512%20512'%20xmlns='http://www.w3.org/2000/svg'%20width='512'%20height='512'%3e%3cdefs%3e%3c!--%20The%20gaps%20in%20the%20rings:%20one%20column%20and%20one%20row,%20cut%20out%20of%20both.%20--%3e%3cmask%20id='mk-rings'%3e%3crect%20width='512'%20height='512'%20fill='%23fff'/%3e%3crect%20x='234'%20y='0'%20width='44'%20height='512'%20fill='%23000'/%3e%3crect%20x='0'%20y='234'%20width='512'%20height='44'%20fill='%23000'/%3e%3c/mask%3e%3c/defs%3e%3cg%20mask='url(%23mk-rings)'%20fill='none'%20stroke='%23ffffff'%20stroke-width='26'%3e%3crect%20x='96'%20y='96'%20width='320'%20height='320'%20rx='92'/%3e%3crect%20x='152'%20y='152'%20width='208'%20height='208'%20rx='62'/%3e%3c/g%3e%3ccircle%20cx='256'%20cy='256'%20r='70'%20fill='%23ffffff'/%3e%3c/svg%3e){kind=small}
Installation
TableCore is a desktop application. It runs on your machine, connects to your MongoDB servers directly, and does not proxy your queries through a service we operate.
What is published today
Windows x64 is the only platform with published builds. macOS and Linux have a working build path in the repository, but nothing is published for them, and the download page lists both as Planned. There is no date, and no beta channel to join.
| Platform | Status |
|---|---|
| Windows x64 | Published |
| macOS | Planned — nothing published |
| Linux | Planned — nothing published |
If the download page shows Windows as Unavailable rather than offering an installer, the public release catalog is momentarily unreadable. That is not the same as Planned: come back rather than looking for a mirror.
Install on Windows
- Open the download page and take the current
Setup.exe. Older builds, with their file sizes and SHA-256 checksums, stay listed in the release archive. - Run the installer.
- Windows will warn you about the publisher. That is expected — read the next section before you click anything.
Installers are served only from releases.tablecore.dev. If you were sent a
TableCore installer from anywhere else, do not run it.
The SmartScreen warning
TableCore's Windows installers are not code-signed. Windows therefore cannot tell you who published the file, and Microsoft Defender SmartScreen shows Windows protected your PC — unknown publisher before it will run.
This is Windows working correctly. It is not a bug in the installer, and it is not something you should route around out of habit.
To continue past it, choose More info, then Run anyway. If you would rather verify the file first, compare its SHA-256 checksum against the value published beside it in the release archive:
Get-FileHash -Algorithm SHA256 .\TableCore-Setup.exe
What an unsigned build does and does not mean
A checksum proves the file you have is the file we published. It does not prove who we are — only a code-signing certificate does that, and TableCore does not have one yet. Until it does, Windows is right to treat the installer as unverified, and you are right to decide for yourself whether to run it.
Where TableCore keeps your data
Everything TableCore stores about you lives in one directory:
%LOCALAPPDATA%\TableCore
| File or folder | What is in it |
|---|---|
settings.json | Interface preferences and connection profile metadata — never a connection string |
workspace.json | Open query tabs, their text, and the selected connection, database and collection |
history.json | Executed query text and timings, kept for 30 days — never result rows |
logs\ | Application logs, with secrets redacted |
backups\ | The default destination for backups, unless you set another one |
Connection strings and SSH credentials are not in any of these files. They are held in the Windows Credential Manager through the operating system's own credential store — see Credentials and secrets for exactly what lands where.
Two environment variables move the whole set, which is useful for a portable install or a shared machine:
TABLECORE_DATA_DIRECTORY overrides %LOCALAPPDATA%\TableCore
TABLECORE_LOG_DIRECTORY overrides the logs directory alone
How updates arrive
Windows builds update through Velopack on the
win-x64-stable channel. Versions are Year.Feature.Fix, so 2026.1.0 is the
first feature release of 2026.
TableCore asks the update feed once when the window opens. If a newer build exists it downloads in the background and the title bar tells you when it is ready to apply — applying it is your decision, and nothing restarts without it. Help → Check for updates asks again at any time, and is the only path that reports a failed check out loud; a background check that cannot reach the feed stays quiet, because it is not something you can act on.
Your open tabs survive the restart: the session is written to disk before the updater takes over.
A build you compiled yourself does not update
The update path exists only for a copy installed by the Velopack installer. A development build run from source has no update feed to ask, so the interface is absent rather than present and failing.
Uninstalling
Remove TableCore from Settings → Apps → Installed apps like any other Windows application.
Uninstalling does not remove %LOCALAPPDATA%\TableCore, so your connection
profiles, workspace and query history survive a reinstall. It also does not
remove the connection strings held in Windows Credential Manager — deleting a
connection profile inside TableCore is what removes its secret. If you are
decommissioning a machine, delete the profiles first, or clear the
TableCore entries from Credential Manager by hand.
Next
Once TableCore is installed, connect it to a server.