The shop floor,
under control.
Emivara is DynaTek's fabrication control platform. Every part from the PDM vault to the print bed — searched, sliced, approved, printed, and tracked — in one system the whole shop shares.
Access is provisioned by your shop admin · invite only
Fabrication looks
like chaos.
Modern 3D printing hardware is excellent. The workflow around it is not. Most engineering teams stitch together CAD, slicers, and printers with email, Slack messages, and tribal knowledge.
CAD files drift from production reality.
Engineers ship a part. The shop opens the wrong revision. Hours of print time evaporate. No audit trail, no traceability.
Operators repeat the same manual steps daily.
Open SolidWorks. Export STL. Open PreForm. Set supports. Sign off. Repeat — forty times, across multiple workstations and printers.
Failures are invisible until they aren't.
Resin tanks run dry mid-print. Print beds jam. No one knows for hours. There is no single source of truth across the fab floor.
Anyone can print anything.
There is no controlled queue, no approval gate, no role separation between request, validate, slice, approve, print.
Twelve stages.
Zero ambiguity.
Every job moves through the same canonical state machine. Each transition is timestamped, attributed, and immutable. Operators always know where a job is — and where it's been.
Requested
An engineer files a job — selects CAD revision, printer, material, quantity, and priority.
File located
The Emivara Agent finds the source CAD on the fabrication workstation’s PDM share.
CAD validated
SolidWorks is driven via the COM API. Geometry, units, and mass properties are confirmed.
Exporting
STL or 3MF is generated with policy-controlled export settings — no manual dialogs.
STL ready
Exported geometry is checkpointed and uploaded as a job artifact for audit.
Slicing
PreForm or Bambu Studio runs headlessly. Slice profile is enforced by org policy.
Awaiting approval
An admin or engineer reviews sliced output, material draw, and time estimate before dispatch.
Approved
A human approval is recorded — actor, timestamp, role — into the immutable event log.
Sent to printer
Emivara dispatches the sliced job to the routed printer based on material compatibility.
Printing
The Agent streams progress, bed/nozzle temps, layer count, and faults back to the cloud.
Complete
Job terminates cleanly. Artifacts and the event ledger are retained for traceability.
Failed
Any non-recoverable error transitions here. Operators see context, root cause, and history.
The full CAD-to-print
control loop.
Every signal — CAD file, automation, slicer, printer firmware, operator approval — is captured by the Emivara Agent and surfaced in the cloud control plane.
Engineered like
production hardware.
Stateful job queue
Twelve canonical job states from Requested through Complete. Every transition is logged. No job is ever in an undefined condition.
CAD-aware automation
Emivara drives SolidWorks directly. Open the part, validate units and mass props, export to STL or 3MF with controlled settings.
Slicer integration
PreForm and Bambu Studio are driven headlessly. Profiles are policy-enforced. Approvers see slice output before anything prints.
Material profiles
Inventory, vendor, cost, and printer compatibility tracked per material. Jobs route to printers that match the selected profile.
Realtime telemetry
Bed temps, resin levels, layer count, print progress — streamed live from the Emivara Agent over an authenticated channel.
Approval gates
Production jobs require explicit approval from an admin or engineer before dispatch. Audit trail is permanent.
Role-based access
Five roles — owner, admin, engineer, operator, viewer — enforced at the database layer.
Built for multi-org
Every record carries an organization_id. Row-level security keeps tenants separated.
The bridge between
cloud and shop floor.
The Emivara Agent runs on a Windows fabrication workstation. It owns the local CAD share, drives SolidWorks, runs the slicer, and talks to printers — all under controlled commands from the cloud.
Access is
controlled.
Emivara is built for environments where uncontrolled access to fabrication hardware is unacceptable. Engineering teams, defense R&D, regulated production, prototype shops — anywhere fabrication output must be controlled, audited, and signed off.
Row-level security.
Every row in every table is filtered by organization_id and user role at the database layer — not in application code. Tenant data never crosses boundaries.
Owner-controlled invites.
Anyone with an invite link from an owner or admin can join. Roles are set per-invite and enforced everywhere the user touches.
Email-verified accounts.
Every account requires email confirmation before the first sign-in. No backdoors, no anonymous access, no shared logins.
Five-role model.
Owner, admin, engineer, operator, viewer. Each role has explicit privileges. Printers, files, and jobs respect the model.
Bring fabrication
under control.
Everything the shop fabricates, in one controlled pipeline — from the CAD vault to the finished part. Sign in to pick up where the floor left off.
Need access? Ask your shop admin to send an invite.