VS Code med Copilot-förslag

Maestro — AI-first test automation

Describe what to test in plain language and your own AI assistant generates a working, version-controlled test in minutes — often with zero hand-written code. Maestro is a modern, cross-platform alternative to NI TestStand and LabVIEW, on Linux, macOS and Windows.

Maestro launches later in 2026. Register now and we’ll tell you the moment you can get it — no obligation.

Request early access
E-Sharp no text
E-Sharp no text white
25+ years building production test systems
Self-hosted — you own your data
Runs on Linux, macOS & Windows
Tests in open, readable YAML in Git — never locked in

Test tools built for a previous era

NI TestStand and LabVIEW are capable tools — but they were built before AI wrote code, before teams lived in Git, and before infrastructure ran anywhere. That shows up on the bench every day:

  •   Test logic lives in binary sequence files an AI can’t read and a diff can’t show.
  •   Results arrive as log files you parse by hand instead of data you can query.
  •   You’re tied to Windows and proprietary hardware, whether or not it suits your line.

Maestro was designed for the way engineers actually work now.

daniel-rhodin-holding-accordion-a2

From intent to a working test — in minutes

stock-photo-number-1

Describe the intent

In plain language, tell your own AI assistant what to measure and the limits — e.g. “check the HDMI output is between 4.9 V and 5.1 V.” No sequence editor and no boilerplate to learn first.

depositphotos_60704955-stock-photo-number-2

Your AI drafts the test

Your AI coding assistant — the one your team already uses, such as Copilot in VS Code — generates the test. Maestro definitions are open, readable YAML, so it writes them directly, often with zero hand-written code.

1000_F_100619345_HMdhlghK2YwussE9tfTuystKxfJ8UZUc

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 version of the test that produced it.

Three parts, one platform

Maestro is a stack you can explore live. Engineers and their AI author tests in the Maestro app; operators run them on any station from the browser-based Operator UI; and the Maestro Server turns every run into queryable data. One platform, from intent to results.

Maestro — AI-first authoring

Describe what to test in plain language and your own AI assistant drafts the test as readable YAML in Git. Review the diff, approve, and you’re ready to run.

Operator UI — run from any browser

Operators launch and monitor tests on any station from a browser — no Windows client to install, no per-seat lock-in. Live status and pass/fail as each unit runs.

Maestro Server — data, not log files

Every measurement is written as a structured row in PostgreSQL, not buried in a per-unit log file — so results, Cpk, yield and a live fleet monitor are all queryable in SQL.

Every measurement is a structured, traceable row

Where TestStand writes each run to a report or log file you have to parse after the fact, Maestro writes every measurement as a structured row in a PostgreSQL database the moment it’s taken — with its limits, verdict and the exact test version attached. Process capability, yield and 3-sigma analytics live in SQL, not in a folder of logs, so out-of-spec and marginal measurements surface before they cost you.

Production dashboard — live station status, yield trends and failure Pareto across the line.

Test results — every report searchable by serial number or test name.

Process capability — Cpk, yield and 3-sigma analytics, queryable.

Fleet monitor — a real-time view of every station’s state and recent runs.

Traceability, built in. Every result carries its serial number, the exact test version, the limits applied and the verdict — so you can trace any measurement back to precisely how and when it was produced, and forward across every unit that shares it. That same structure is what makes the data AI-ready: an assistant can query it, spot drift across units, correlate failures and explain a result, because each row has meaning rather than being text to parse.

How Maestro compares to NI TestStand & LabVIEW

Maestro by E#

Authoring: AI-first and intent-based — readable YAML in Git

Platform: Linux, macOS & Windows (Docker + browser UI)

Results: queryable data — Cpk, yield and trends in SQL

Data model: every measurement a structured row in PostgreSQL, with limits and test version attached

Your data: self-hosted — you own and run it

NI TestStand / LabVIEW

Authoring: GUI sequence editor — binary, AI-opaque files

Platform: Windows-centric

Results: log files and manual parsing

Data model: results written to per-unit report / log files

Your data: varies, often tied to vendor tooling

When Maestro is a fit

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 or why a limit was set.
  • You want your test data structured and queryable the moment it’s captured, not parsed out of log files after the fact.

It scales from a single bench at an SME to hundreds of stations across a large operation — start with one line and grow.

Be first to run Maestro

Maestro launches later in 2026. Register your interest and you’ll be the first to know the moment it’s available to get.

Check the pricing first

A licensing model TestStand users recognise — annual developer and runtime licenses, self-hosted, with your tests in open formats that stay yours. View the full pricing model.

Frequently asked questions

Is Maestro an alternative to NI TestStand and LabVIEW?

Yes. Maestro is a modern, AI-first test-automation platform for teams moving beyond NI TestStand and LabVIEW. Test definitions are readable YAML 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 your own AI assistant 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 your own AI assistant turns it into an executable, version-controlled test in minutes, instead of you hand-building it in a sequence editor.

Does Maestro run on Linux and macOS, or only Windows?

Cross-platform. The stack runs in Docker on Linux, macOS and Windows, and the operator interface is browser-based — no Windows or proprietary-hardware lock-in.

Who owns my test data?

You do. Maestro is self-hosted: you run the hosting and the PostgreSQL database yourself. E-Sharp measures no usage and holds none of your data.

Are my tests locked into Maestro?

No. Test definitions are stored as readable YAML in your own Git repository. The format is open and stays yours; only the engine that runs them is licensed.

Which instruments does Maestro support?

Drivers for E-Sharp’s Accordion test hardware are available. For broader instrument support, talk to us about your setup — get in touch via the early-access form.

What does “early access” mean right now?

Maestro is pre-launch. Registering means we contact you directly the moment Maestro is available to acquire, with no obligation in the meantime.