G-Code Verification Platforms — History and Evolution

Vericut's strengths trace directly back to the length and breadth of its history. Four decades of continuous development, tested against an enormous and varied population of real machines, real controls, and real programs, is not something a competitor can shortcut regardless of how well-funded or well-engineered a newer entrant might be. That accumulated experience shows up less as any single headline feature and more as a general absence of surprises: edge cases that would trip up a younger simulation engine — an unusual macro construct, a rarely used canned cycle, an obscure interaction between two synchronized channels — have, in most cases, already been encountered and handled somewhere in Vericut's history.

• Unmatched maturity and track record. Vericut has been in continuous commercial use longer than either of its major competitors, and that time has been spent almost entirely on refining a single core discipline — collision and material-removal simulation — rather than dividing attention across unrelated product lines.
• Exceptional breadth of machine and control support. Because CGTech's customer base spans nearly every corner of precision manufacturing, its machine and control library has grown correspondingly broad, covering an unusually wide range of builders and controllers rather than concentrating on any one region or machine class.
• Deep Swiss-type and multi-channel capability. Guide bushings, bar feeders, part catchers, and synchronized multi-spindle motion are all modeled with a level of detail that reflects real investment in this specific, demanding corner of machining, not a generic afterthought bolted onto a mill-focused product.
• Optimization built on the same verified model. The Force module means a shop isn't forced to treat verification and cycle-time optimization as two separate problems solved by two different tools that might quietly disagree with each other about how the machine actually behaves.
• CAM-agnostic by design. Vericut verifies posted G-code rather than an internal CAM toolpath, which means it works identically well regardless of which CAM system, or combination of CAM systems, actually produced the program — a real advantage for shops running mixed programming environments.
• Reputation in the highest-consequence industries. Aerospace, medical device manufacturing, and motorsports all lean on Vericut specifically because the cost of a single mistake in those fields is so severe; that reputation carries real weight when a shop is choosing a verification platform it needs to trust completely.
• Independent, focused ownership. Remaining privately held for its entire history has let CGTech keep its attention on machining simulation as its sole business, rather than sharing product priorities with a much larger, more diversified corporate parent.
• Active, well-funded ongoing development. Recent releases show a company still investing meaningfully in the product, including newer AI-assisted features aimed directly at softening the learning curve that has long been one of the platform's most common criticisms.

Vericut's limitations are, in large part, the flip side of the same history that gives it its strength. A product this old and this feature-rich inevitably accumulates complexity, and a company that has spent decades serving the most demanding, highest-budget corners of manufacturing has not always had the same incentive to keep its licensing and onboarding simple for a smaller shop evaluating it for the first time.

• A genuinely steep learning curve. The scope of what Vericut can do is also the scope of what a new user has to learn; a programmer coming from a simpler tool can find the sheer number of settings, modules, and configuration options overwhelming before they've simulated their first real program.
• Licensing costs that scale quickly. Base verification is only the starting point — machine-specific configuration files, the Force optimization module, and additional seats for multiple programmers can each add meaningfully to the total cost, and a shop that wants the full capability set should expect a substantial ongoing investment.
• Machine model maintenance is an ongoing burden. Because Vericut is a separate application from whatever CAM system actually generates a program, each machine's configuration file — describing its exact kinematics, tooling, and fixtures — has to be built accurately and then kept in sync as the real machine changes over time; this is real, recurring work rather than a one-time setup cost.
• Real effort required to onboard a new or unusual machine. Building an accurate configuration for a machine that doesn't already have a well-established profile in CGTech's library can take meaningful time and specialized expertise, which is a real barrier for a shop bringing in newer or less common equipment.
• Can feel like more tool than a small shop needs. Vericut's depth is a genuine advantage for a large, complex operation running dozens of machines across multiple facilities, but that same depth can feel disproportionate — in both cost and complexity — for a small job shop that mainly needs straightforward collision checking on a handful of machines.
• An added application and workflow step. Regardless of how well it's integrated, Vericut still represents a separate piece of software sitting outside the CAM environment where a program was actually written, which means an extra export-and-import step in every programmer's workflow rather than a single unified environment.

NCSIMUL's roots reach back to the early 1980s in France, where a company called Spring Technologies began working on the same fundamental problem that CGTech was tackling on the other side of the Atlantic at almost exactly the same time: how to prove a CNC program correct before committing real machine time to it. Where Vericut grew up largely within the orbit of American aerospace manufacturing, Spring Technologies built its business primarily around European industry, developing especially close relationships with machine tool builders and precision manufacturers across France and Germany. For most of its first three decades, NCSIMUL existed as a distinctly European alternative to the American-led simulation market, well known within that market but far less visible outside it.

Rather than treating simulation as a single, standalone product, Spring Technologies gradually built NCSIMUL into a broader suite spanning the full lifecycle of an NC program. Alongside the core machine-verification engine, the company developed Optitool, aimed at reducing wasted non-cutting motion and tightening feed rates; NCdoc, which automatically generates shop-floor documentation synchronized to the actual verified simulation rather than a separately maintained paper process; and 4CAM, built to let an existing program be retargeted to a different machine without sending it back through the original CAM system. A visualization mode marketed under the name WYSIWYC — a deliberate echo of the familiar "what you see is what you get" phrase from desktop publishing — became one of the product's signature features, built around giving a programmer real-time, synchronized 3D feedback that closely mirrors what the actual machine control would display.

That steady, suite-oriented development earned recognition within the European CNC industry over the years, including an Innovation Trophy at the Industrie Paris trade show in 2016 for the way NCSIMUL CAM simplified switching between machine configurations and managing post processors — a genuinely difficult problem for any shop running a mixed fleet of equipment. By that point, Spring Technologies had accumulated more than three decades of continuous investment in the underlying simulation technology, positioning the company as a serious, if still largely regionally concentrated, player in CNC verification.

The most consequential turning point in NCSIMUL's history came in 2018, when Hexagon AB — a large, diversified Swedish measurement-technology company with a portfolio spanning metrology, geospatial systems, and industrial software — acquired Spring Technologies outright. The company was subsequently renamed and folded into what is now Hexagon's Production Software division, adopting the Hexagon corporate identity while, by most accounts, retaining much of its original French engineering team and technical direction. The acquisition gave the product access to a dramatically larger corporate parent's resources, global sales channels, and — perhaps most significantly for existing customers — a natural connection to Hexagon's much broader portfolio of metrology and quality-inspection tools, letting verification data and measurement data begin to speak a shared language for shops already invested in that wider ecosystem.

Since the acquisition, development has continued at a steady pace under Hexagon's ownership. Recent releases have introduced features like GPU-accelerated Selective Simulation, which generates intermediate stock previews during program decoding so that a programmer working with a very long, complex multi-channel file can jump directly to the sections that need closer attention rather than waiting for a full linear simulation to reach them. That kind of investment suggests Hexagon has continued to treat NCSIMUL as a genuine product priority rather than a shelved acquisition, even as it now competes for development resources against a much wider set of businesses inside a much larger company.

• 1983Spring Technologies begins developing early CNC simulation software in France, roughly contemporaneous with CGTech's origins in the United States.
• 1980s–2000sThe company builds deep relationships with European machine tool builders and precision manufacturers, particularly in France and Germany.
• OngoingThe NCSIMUL suite expands to include Optitool (cutting optimization), NCdoc (automated shop documentation), 4CAM (machine retargeting), and the WYSIWYC real-time visualization mode.
• 2016NCSIMUL CAM receives an Innovation Trophy at the Industrie Paris trade show for simplifying machine-configuration and post-processor management.
• 2018Hexagon AB acquires Spring Technologies; the product and company are rebranded and absorbed into Hexagon's Production Software division.
• 2026Hexagon introduces GPU-accelerated Selective Simulation, using early rest-stock previews to speed up review of long, complex multi-channel programs.

NCSIMUL's particular strengths reflect both its European engineering origins and the scale it gained by joining a much larger organization. It reads less like a single-purpose verification tool bolted onto a bigger product line and more like a genuinely integrated suite that happens to have collision checking at its foundation.

• Deep, well-established European machine and control coverage. Decades spent building relationships with European machine tool builders translate into an unusually strong out-of-the-box library for the kind of Swiss-type and precision-turning equipment especially common across that region.
• A genuinely broad product suite, not just a checker. Optitool, NCdoc, and 4CAM extend the same core platform into cutting-condition optimization, automated documentation, and cross-machine program portability, giving a shop real capability beyond pure collision detection from a single vendor relationship.
• The backing of a large, well-resourced parent company. Being part of Hexagon means access to a global sales and support network, sustained R&D investment, and financial stability that an independent company of Spring Technologies' original size would have struggled to match on its own.
• Real integration value for Hexagon's existing customers. A shop already using Hexagon equipment or software for inspection and quality control has a genuine, practical reason to prefer NCSIMUL, since verification and metrology data can share more of the same underlying ecosystem.
• Straightforward CAM data import. The software is built to pull in existing programs, origins, geometry, and tool data directly from a shop's CAM system, reducing the amount of manual re-entry required to get a program ready for simulation.
• Real-time, synchronized visualization. The WYSIWYC mode gives programmers 3D feedback that closely tracks what would actually appear on the machine's own control screen, narrowing the gap between what's simulated and what's experienced on the shop floor.
• Continued visible investment post-acquisition. Recent additions like GPU-accelerated Selective Simulation show Hexagon actively modernizing the platform rather than leaving it to stagnate after the acquisition, which is not a guarantee every acquired product receives.

NCSIMUL's limitations largely mirror the flip side of its regional history and its position inside a much larger corporate structure. A product that spent its first three decades focused primarily on one continent, and that now shares a roadmap with a much broader business, carries some structural trade-offs that are worth weighing honestly.

• Smaller footprint outside Europe. Despite considerable growth since the Hexagon acquisition, NCSIMUL's installed base and name recognition in North America and Asia still lag behind Vericut's, which can translate into fewer local peers, integrators, and experienced hires to draw on in those markets.
• Thinner independent community and training resources. A smaller global footprint tends to mean fewer public forum discussions, third-party tutorials, and shared troubleshooting knowledge outside official vendor channels, compared to a much longer-established competitor.
• Product priorities shared with a much larger, diversified business. As one line within Hexagon's much broader manufacturing and metrology portfolio, NCSIMUL's specific development priorities are not the only thing competing for Hexagon's attention and investment, which introduces a degree of dependency a fully independent company wouldn't have.
• Disruption inherent to any major rebranding. The transition from an independently known "Spring Technologies" product to a Hexagon-branded one, however smoothly executed, represents exactly the kind of identity and continuity shift that can create friction for existing customers and complicate a newcomer's research process.
• Still an added license and workflow step. Like any standalone verification platform, NCSIMUL sits downstream of a shop's CAM system rather than inside it, meaning programs still need to be exported and imported as a distinct step in the overall workflow.
• Historical brand recognition gap in some markets. Even where the technology itself is fully competitive, a shop evaluating verification software for the first time in North America is, on average, considerably more likely to have already heard of Vericut than NCSIMUL, which can shape which products even make it onto a shortlist.

Eureka's history begins somewhere neither Vericut's nor NCSIMUL's does: not in simulation at all, but in post-processing. Roboris was founded in Pisa, Italy, in 2001 by two engineers, Mirko Sgarbi and Gianluca Bioli, whose earliest work involved writing custom post processors for major CAD/CAM platforms of the day, including Pro/ENGINEER and CATIA. That starting point matters more than it might first appear, because a post processor sits at the exact seam between a CAM system's generic internal toolpath and the specific, literal G-code a real controller will execute — and spending years working precisely at that seam gave the company's founders an unusually detailed, hands-on understanding of exactly where things tend to go wrong between a toolpath's intent and a machine's actual behavior.

By around 2005, that accumulated post-processing expertise led Roboris to a pivot: rather than continuing purely as a post-processor specialist, the company shifted its primary focus to building its own machine simulation software from the ground up. According to the company's own account of its history, this move was driven in part by a chance connection with a researcher who had completed doctoral work specifically on material-removal simulation — the genuinely hard computational-geometry problem of accurately modeling how a moving tool actually carves material away from a solid stock. Bringing that expertise in-house let Roboris build a simulation engine as proprietary, from-scratch technology rather than licensing one from an outside supplier, which meant the company had complete control over every layer of the resulting product, from the underlying collision math up through the user interface a programmer actually sees.

What set Roboris's approach apart from the beginning was its insistence on verifying the actual G-code a machine would run, rather than an intermediate representation generated inside a CAM system. Because the founders had spent years thinking about exactly what a post processor introduces or changes on the way from toolpath to G-code, building a simulator that verified the finished file — including whatever a post processor, a hand edit, or a synchronization command had introduced along the way — was a natural extension of that background rather than an afterthought.

Over the following two decades, Eureka grew from a single simulation product into a family of purpose-specific modules. Eureka G-Code (also offered in a lighter form as Eureka3X for simpler 3-axis milling work) handles core verification. Eureka NC Coder was built specifically around the workflow of programming Swiss-type and multi-channel mill-turn machines — assigning toolpaths to the correct channel, inserting synchronization and part-transfer commands, generating code through Eureka's own built-in post processor, and verifying the result, all inside one connected environment rather than across several disconnected tools. Eureka Chronos added automated cutting-condition optimization, and Eureka Robot extended the same underlying simulation technology into off-line programming for industrial robots, a related but distinct market Roboris moved into as the company matured. A free companion tool, Eureka Viewer, was introduced to let a saved simulation be shared and replayed by anyone on a shop floor without requiring a paid license — a deliberately low barrier to getting a verified program in front of the person actually running the machine.

Roboris has remained privately owned throughout its history, a fact the company itself points to as a meaningful part of its identity, describing its independence as freedom to make fast product decisions and offer responsive support without needing to satisfy outside investors. That independence, combined with the company's continued focus on Swiss and multi-channel mill-turn machining as a core specialty rather than one segment among many, has allowed Eureka to build a customer base spanning more than forty countries — including, by the company's own case studies, small independent shops taking on increasingly complex multi-axis Swiss work who found the combination of NC Coder's synchronization-focused workflow and Eureka's simulation accuracy made hand-coded multi-channel programming meaningfully less error-prone.

• 2001Roboris is founded in Pisa, Italy, by Mirko Sgarbi and Gianluca Bioli, initially building custom post processors for platforms including Pro/ENGINEER and CATIA.
• c. 2005The company pivots to building its own in-house simulation engine, aided by newly acquired expertise in material-removal simulation, and shifts its primary focus to full machine verification software.
• 2000s–2010sThe Eureka product family expands beyond core G-code verification into Eureka Chronos (cutting-condition optimization) and Eureka Robot (off-line robot programming).
• OngoingEureka NC Coder is developed specifically around Swiss-type and multi-channel mill-turn programming, tightly integrating toolpath import, channel synchronization, post-processing, and verification.
• OngoingEureka Viewer is released as a free companion tool, letting saved simulations be reviewed on the shop floor without a paid license.
• RecentRoboris continues to expand distribution across more than forty countries and adds support for validating AI-generated toolpaths alongside traditionally programmed ones.

Eureka's strengths follow directly from its unusual starting point. A company that began by living inside the post-processing problem, and that later chose to specialize deeply in Swiss and mill-turn machining rather than trying to cover every corner of CNC equally, tends to produce a product that feels genuinely built for that specific job rather than adapted to it after the fact.

• Built around Swiss and mill-turn programming from the start. The Eureka NC Coder workflow was designed specifically for the problem of assigning toolpaths to channels, inserting synchronization commands, and verifying the result — arguably the single most error-prone part of multi-channel Swiss programming — rather than treating it as a secondary use case.
• Verifies the actual finished G-code, not an intermediate toolpath. Because of its post-processing heritage, Eureka catches problems introduced after a CAM system has already done its job — in the post processor itself, in a manual edit, or in hand-added synchronization logic — that a tool simulating only the CAM-internal toolpath would never see.
• A fully in-house, proprietary simulation engine. Having built its own geometry and collision-detection technology from scratch rather than licensing it from an outside supplier, Roboris has complete control over the entire stack, letting it move quickly on features specific to its core market.
• Pricing and packaging accessible to smaller shops. Eureka is generally positioned as more approachable, both in cost and in complexity, than the full module lineup of a much larger, longer-established competitor, which matters for smaller job shops evaluating verification software for the first time.
• A free viewer that lowers the barrier to shop-floor adoption. Eureka Viewer lets a verified simulation be shared and played back by an operator without requiring that person to hold a full license, making it easier to actually get a verified program in front of the people running the machine.
• Privately owned and, by its own account, unusually agile. Answering to customers rather than outside investors, Roboris presents its comparative size as an advantage in responsiveness — able to build genuinely deep support for a narrow specialty rather than treating it as one of many competing priorities.
• Actively expanding into adjacent capability. Newer modules extending the same core platform into robot programming and AI-assisted cutting optimization suggest a company still growing its scope deliberately, rather than one standing still on a single legacy product.

Eureka's limitations are, in large part, simply the natural consequences of being a smaller, more specialized company competing against two much larger and longer-established rivals. Specialization is a genuine strength within its core market, but it comes with real trade-offs outside that market.

• Smaller company and installed base than either major competitor. Roboris is meaningfully smaller than both CGTech and Hexagon, which shows up in a thinner overall ecosystem of independent integrators, trainers, and long-time users to lean on when something unexpected comes up.
• Narrower machine and control library outside its core focus. Eureka's depth in Swiss and mill-turn kinematics is a real advantage for shops working in that niche, but its breadth of support for less closely related machine types and controllers is correspondingly narrower than Vericut's far more extensive general-purpose library.
• Less historical brand recognition in the highest-consequence sectors. Aerospace and other extremely risk-averse industries have, over decades, built strong institutional familiarity with Vericut in particular; Eureka's more specialized, mill-turn-centric history means it has less of that built-in trust to draw on in sectors outside its core strength.
• Company scale can matter for very large, multi-site rollouts. A smaller organization may have less bandwidth to support an extremely large enterprise customer standardizing verification software across many facilities simultaneously, compared to a company with the global infrastructure of Hexagon or the decades-long enterprise relationships CGTech has built.
• A comparatively recent entrant into simulation specifically. While Roboris itself dates back to 2001, its dedicated simulation focus only began around 2005 — meaningfully later than either Vericut's or NCSIMUL's roots in the early-to-mid 1980s — giving it a shorter track record in this specific discipline even though its post-processing pedigree runs deep.
• Still an added application and workflow step. Like its competitors, Eureka verifies G-code downstream of whatever CAM system produced it, meaning it remains a separate piece of software and an additional step in a programmer's overall process rather than a feature built directly into an existing CAM seat.