Skip to content
TaktSignal

Docs / Start here · Community Alpha

Getting started

TaktSignal is Manufacturing Operational Intelligence for ERPNext. It reads your ERPNext sales orders, work orders, stock and purchase orders and shows where the factory is about to lose time — material shortages, stalled or late work, overloaded work centers and customer orders at risk — with the reason, the evidence and how sure it is. It also checks whether the numbers behind each warning can be trusted.

Community Alpha — early public testing. TaktSignal has been through substantial automated, synthetic and internal testing, but it has not yet been validated across enough real factories, ERPNext set-ups and computers. Start with a staging or test copy of ERPNext, compare what TaktSignal says with ERPNext and the shop floor, and do not use it as the only basis for production decisions. See Community Alpha limitations.

TaktSignal is not an ERP, not an MES and not a scheduler. It never changes anything in ERPNext.

What you need

  • A computer: a Mac with Apple Silicon (macOS 12 or later), or a 64-bit Ubuntu 22.04+ / Debian 12+ PC with a desktop session. Windows 10/11 is experimental. 4 GB of memory and 2 GB of free disk space.
  • Someone who can create a user and a role in ERPNext (usually your ERPNext administrator) — about 10 minutes.
  • About 10 minutes for setup, plus the first data read (a few minutes for a small factory).

No terminal, Docker, database or programming is needed.

The happy path

  1. Download. Go to taktsignal.cloud/download and choose your computer. Read the notes on the card before you download — the Community Alpha is an unsigned test build, and the card says what your computer will show. (Installation, verify the download)
  2. Install. macOS: drag TaktSignal into Applications and approve it once (macOS guide). Linux: open the .deb with the App Center. Windows (experimental): Windows guide.
  3. Launch. TaktSignal opens its Control Center in your web browser. It runs only on your computer — nobody else on the network can open it.
  4. Welcome and safety. Read what TaktSignal does with your data, then confirm you will connect a staging, test or lab copy of ERPNext.
  5. System check. TaktSignal checks disk space and your computer's password store and prepares its own local database. Nothing to do.
  6. Create the local administrator — your name, e-mail and a password of at least 12 characters. This account exists only in your TaktSignal; it is not an ERPNext account.
  7. Create a dedicated TaktSignal Reader in ERPNext — a user that can only read. Never use Administrator or your own login. (ERPNext Reader setup)
  8. Enter the ERPNext address, API key and API secret. The key and secret go into your computer's password store. (Connect ERPNext)
  9. Choose your company (chosen for you if there is only one).
  10. Read-only verification. TaktSignal checks that the Reader cannot create, change, submit, cancel or delete anything. If it can, setup stops and tells you what to remove. This cannot be skipped.
  11. Capability check. You see which parts of TaktSignal are ready, limited or unavailable with this Reader, and why.
  12. Initial synchronization. TaktSignal reads your data once. (First sync)
  13. Data Trust review. How complete and fresh the data is, and what will lower confidence. (Understanding Data Trust)
  14. Open TaktSignal and sign in with your local administrator. Start on the dashboard. (Using TaktSignal)

After setup

  • TaktSignal reads ERPNext again in the background (every 15 minutes by default) and starts when you log in to your computer. You can turn the start at login off in Control Center → Advanced.
  • Check alerts against ERPNext and the floor before acting. Understanding alerts explains how.
  • Back up from Control Center → Backups. (Backup and restore)

Your data

TaktSignal keeps a copy of the ERPNext data it reads in a database on your computer. It sends no telemetry, collects no usage analytics and sends no factory data to TaktSignal or to AI services. Privacy and your data explains exactly what is stored and what leaves the computer.

Getting help

Control Center → Help & diagnostics → Export diagnostics, then report the problem as described in Diagnostics and support. Never post API keys, passwords, backups or customer data publicly.