Community Alpha · Early public testing
Help validate TaktSignal with real ERPNext environments.
TaktSignal has been through substantial automated, synthetic and internal validation, but it has not yet been validated across enough real factories, ERPNext configurations and desktop environments. Community Alpha exists to gather that evidence.
What you are joining
You are helping validate an early product. TaktSignal is free to download during Community Alpha. It runs on your own computer, reads your ERPNext with a read-only account, and keeps its data there — we never receive your factory data. What we ask in return is honest feedback: what it got right, what it got wrong, and where it was confusing.
Who should test
ERPNext users in manufacturing
You run production, stock and purchasing in ERPNext and want to know where time is about to be lost.
Manufacturing SMEs
Small and mid-sized discrete manufacturers — apparel and textile first, other assembly and fabrication welcome.
Operations and production managers
The people who start the day asking what will be late and why.
ERPNext implementers
Consultants who can test against several client configurations (with test copies, not client data in public).
Technically curious factory owners
Comfortable installing an early app and giving honest, specific feedback.
Start safely
Connect one of these — not your live production ERPNext:
- 01
An ERPNext staging site
A copy your team already uses for testing.
- 02
An isolated copy of your ERPNext
Restored from a backup onto a separate server, not connected to live operations.
- 03
A lab or test site
A fresh ERPNext with sample or anonymised data.
You should
- use a dedicated read-only ERPNext Reader;
- compare findings with ERPNext and real operations;
- report discrepancies;
- keep backups.
You should not
- rely on the Alpha alone for critical production decisions;
- connect Administrator or other broad credentials;
- publish raw factory information when reporting issues.
Feedback that matters most
- Installation
- Where you got stuck, every warning text, how long it took.
- ERPNext compatibility
- Versions, customisations, statuses or set-ups TaktSignal misread.
- Sync behaviour
- Failed or slow syncs, stale data, permission surprises.
- Incorrect alerts
- Alerts that were wrong — and what was really happening.
- Missing alerts
- Problems you saw coming that TaktSignal did not flag.
- Confidence
- High confidence on something wrong, or low confidence on something obvious.
- Data Trust
- Freshness, completeness or reconciliation results that do not match ERPNext.
- Usability and workflow
- Words you did not understand, steps that do not fit how your factory works.
- Performance
- Slow pages or syncs, with the rough size of your data.
The most useful signal is built in: when you resolve an alert in TaktSignal, record what happened and whether the alert was right. Then tell us what you saw — without customer data — through the support page.
Platforms in this Community Alpha
- macOS — Apple Silicon — Tested Community Alpha
- Linux — x64 (.deb) — Tested Community Alpha
- Windows — x64 — Experimental Community Alpha
- macOS — Intel — Pending — not validated