1
Describe the intent
Tell the assistant what to measure and the limits — e.g. “check the HDMI output is between 4.9 V and 5.1 V.” Plain language, no sequence editor.
AI-first test automation — from intent to a working test in minutes.
Maestro is the only platform where AI-powered, intent-based test development and project tracking are seamless. Describe what to test in plain language; the assistant — trained on test development and electronics engineering — turns your specification into a working test in minutes, often with zero hand-written code. Built for the AI era, not retrofitted onto it: a modern, cross-platform alternative to NI TestStand and LabVIEW that runs on Linux, macOS and Windows.
One connected platform
Maestro is a stack you can explore live. Start in the Maestro app where the AI authors and runs your tests; the Maestro Server turns every run into queryable data; and Trace keeps the engineering knowledge — requirements, decisions and field returns — connected to it all. One AI assistant reasons across the whole thing.
Start here · the heart of Maestro
Maestro
AI-first test automation
Describe what to test in plain language; the assistant drafts the test, you review the diff and run it on a station from any browser — often zero code.
Maestro Server
Dashboard & results
Test results, process capability (Cpk & yield), and a live fleet monitor of every station — every measurement a queryable row, not a log file.
Trace
Knowledge & project management
AI-first requirements, verification coverage, milestones, BOM and decisions — the engineering brain that remembers why, and never forgets.
One shared AI assistant runs across the whole stack — authoring tests, explaining results and reasoning over your requirements and measurements together.
From intent to a working test — in minutes
2
AI drafts the test
An assistant trained on test development and electronics engineering generates the test definition as readable, version-controlled text — often with zero hand-written code.
3
Review & run
You review the diff, approve it, and run it on a station from any browser. Every measurement is stored as queryable data, traced to the exact test version.
One platform, end to end
Production Dashboard
Live station status, yield trends and failure pareto charts across your whole line.
Test Results
Every report, searchable by serial number or test name — every measurement a queryable row, not a log file.
Process Capability
Cpk, yield and 3-sigma analytics in SQL — surface out-of-spec and marginal measurements before they cost you.
Fleet Monitor
A real-time view of every test station — state, progress and recent executions from across the floor.
Trace — project tracking
Requirements, verification coverage, milestones, BOM and component library — the engineering loop, closed.
How Maestro compares to NI TestStand & LabVIEW
NI TestStand and LabVIEW are capable tools, built for a previous era. Maestro was designed for a world where AI writes code, teams live in Git, and infrastructure runs anywhere.
Maestro by E#NI TestStand / LabVIEW
Test authoring
AI-first, intent-based — plain-text definitions in Git
GUI sequence editor; binary, AI-opaque files
Platform
Linux, macOS & Windows (Docker + browser UI)
Windows-centric
Results
Queryable data — Cpk, yield, trends in SQL
Log files and manual parsing
Lifecycle
Built-in project tracking & requirement-to-field traceability (Trace)
Test execution only; lifecycle lives elsewhere
When is Maestro right for me?
Maestro fits teams that build real hardware and care about what their test data means — not just that it was captured. You're likely a fit if several of these ring true:
- You run production or verification tests on electronics and want results as queryable data, not log files.
- You want your team — and its AI agents — to author tests from intent instead of hand-coding sequence editors.
- You're moving beyond NI TestStand / LabVIEW, or off Windows-only, proprietary-hardware lock-in.
- A field return turns into a multi-day investigation because nobody can find the test record, the requirement, or why a limit was set.
- You need requirement-to-field traceability and want coverage gaps visible before an audit or a return — not after.
- You want engineering knowledge to compound as an asset instead of leaking into people's heads, dead wikis and email.
- Any size of operation. Maestro scales from a single bench at an SME to hundreds of stations across a large corporation — start with one line and grow, with no per-seat lock-in to fight you on the way up.
Test and project tracking, finally on one platform
Maestro proves each unit on hardware; Trace remembers why. Together they hold the whole chain — requirement → test → measurement → limit → field return → the rule you change so it never happens again — as one connected, queryable record. Coverage gaps, marginal passes and test escapes become visible, and your organisation's engineering knowledge compounds with every unit it builds and every unit that comes back.
Why E#
E-Sharp AB designs and builds advanced test and data-acquisition systems for hardware companies — electronic, mechanical and FPGA design under one roof. Maestro is the software that runs them.
- 200+ test systems delivered to Axis Communications over five years
- ISO 9001 & ISO 14001 certified for quality and sustainability
- Engineered in Kävlinge, Sweden — concept to final assembly
Sharp minds. Sharp engineering. Sharp innovation.
Frequently asked questions
Is Maestro an alternative to NI TestStand and LabVIEW?
Yes. Maestro is a modern, AI-first test-automation platform built for teams moving beyond NI TestStand and LabVIEW. Test definitions are plain text in Git rather than binary sequence files, results are queryable data, and the operator UI runs in any browser on Linux, macOS or Windows.
Do I need to write code to create a test?
Often not. You describe the test in plain language and the AI assistant, trained on test development and electronics engineering, drafts a working test for you to review and run. Many tests are created with zero hand-written code, and you approve everything.
What is intent-based test development?
You state your intent — what to measure and the limits — and the AI turns that specification into an executable test in minutes. Maestro is the only platform where AI-powered intent-based test development and project tracking work seamlessly together.
Does Maestro run on Linux and macOS, or only Windows?
Maestro is cross-platform. The stack runs in Docker on Linux, macOS and Windows, and the operator interface is browser-based, so it works on any device with no Windows or proprietary-hardware lock-in.
How does Maestro connect test results to requirements and field returns?
Its companion Trace links requirements to tests, measurements, limits and field returns in one queryable record, so coverage gaps, marginal passes and test escapes are visible and every project's engineering knowledge compounds over time.
What is Trace?
Trace is the knowledge and project-management layer of the stack — AI-first requirements, verification coverage, milestones, BOM, a component library and design decisions, all connected. If Maestro proves each unit on hardware, Trace remembers why: what the requirement was, where a limit came from, and what the last engineer decided and rejected. It's where your AI agent reasons across your whole engineering reality, not just one test.
We already store all our test data. Why do we need Trace?
Because data is not knowledge. Your test floor produces perfect facts — this unit, this measurement, this verdict, this version — but a fact can't tell you which requirement it proves, whether your coverage has a hole, or whether a returned unit was a test escape, a marginal pass or a gap you never tested. Trace is the layer that answers those questions, turning a pile of true data into the living knowledge of your product.
How is this different from a requirements tool, ALM or PLM?
Document and ALM tools stop at a design on paper. Maestro plus Trace closes the hardware-in-the-loop right side of the V: requirement → measured production test → structured data → derived limit → field return → the rule you change so it can't recur. That closed loop on real hardware — and the years of real measurements, decisions and returns inside it — is the part a competitor can't simply copy.
Does Trace get more valuable over time?
Yes — it's the only part of the stack whose value compounds. Hardware and test execution do as good a job on unit #1 as on unit #100,000; their value per unit is flat. Every requirement captured, decision recorded, test linked and field return learned from accumulates into one asset that's worth more every year you run it. The organisation literally gets smarter with every unit it builds and every unit that comes back.
info@esharp.se · +46 (0)46-590 01 20 · Götgatan 3, 244 32 Kävlinge, Sweden