Build engineering-file workflows without rebuilding the file layer.
Rine gives software and AI products infrastructure for turning engineering files into structured data, usable representations, and downstream application workflows.
Current Developer Preview: DWG, DXF and DWT inputs.One infrastructure layer. Many product workflows.
Engineering-file infrastructure tends to appear inside products in different forms.
Sometimes you need to extract geometry and metadata. Sometimes you need a renderable representation. Sometimes you need to convert a source file into something the rest of your stack can use. And increasingly, AI systems need engineering information in a structure they can reason over.
Rine is designed so those workflows can share the same normalized foundation instead of becoming separate file-processing systems.
/extract currently accepts real DWG files and returns structured LAVINCI_CAD_IR_V3 together with diagnostics.
Extract structured data from CAD files
Turn an engineering file into something your software can actually work with.
A CAD file should not have to remain an opaque binary dependency inside your product. Use Rine to extract supported engineering files into a structured intermediate representation that downstream systems can inspect, transform, store, or reason over.
- engineering AI products
- CAD ingestion pipelines
- search and indexing systems
- geometry-aware applications
- downstream automation
- internal engineering tooling
Convert engineering files for downstream systems
Give the rest of your stack the representation it actually needs.
Products rarely want an engineering file purely because it is a DWG or DXF. They want something they can display, transmit, process, archive, or feed into another workflow. Rine lets developers build conversion into the product layer without maintaining every conversion path independently.
- export pipelines
- web applications
- previews and thumbnails
- downstream document generation
- integration workflows
- non-CAD data pipelines
Render engineering files inside modern products
Let users see engineering information without embedding the original authoring environment.
Engineering software increasingly lives in browsers, cloud applications, collaboration systems, and AI interfaces. Those products often need a visual representation of a technical file without recreating the entire CAD environment around it.
Rine can produce downstream visual representations from supported inputs for use in product interfaces and processing pipelines.
Vector PDF
High-quality document-style output.
SVG
Vector representations for web and programmable interfaces.
PNG / JPEG / WebP
Raster outputs for previews, thumbnails, AI pipelines, and application UI.
Rine exposes structured engineering information and diagnostics. The reasoning layer remains yours.
Give AI systems structured engineering context
Engineering AI needs more than a filename.
AI systems can reason much more effectively when engineering information is represented as structured data rather than treated as an opaque attachment.
Rine provides a path from engineering files into normalized representations that developers can incorporate into agents, copilots, search systems, and other AI workflows.
- engineering copilots
- technical search
- structured file inspection
- workflow automation
- agent tools for engineering
- retrieval over file contents
Normalize file infrastructure behind a product
Stop letting file formats dictate your application architecture.
Without a common layer, every new engineering format can create another parser, another transformation path, another representation, and another collection of edge cases.
La Vinci is built around a normalized Rine Intermediate Representation so reusable product capabilities can sit downstream of the source format.
Your application owns the product logic. Rine owns the file infrastructure underneath it.
Engineering-file tools for agents
Rine is designed not only for traditional APIs, but for a world in which AI agents need tools for reading, transforming, and working with engineering assets.
The long-term Rine architecture includes APIs, MCP servers, and developer-facing tools around the same engineering-file intelligence layer.
Build against La Vinci's Developer Preview API.
The same infrastructure can become reusable tools for agentic engineering workflows.
Technical documents are part of the same problem.
Engineering workflows rarely consist of CAD files alone.
Drawings, specifications, review packages, reports, submittals, and other technical documents often carry information that software systems can reference but do not actually understand.
Rine's broader engineering-file intelligence thesis includes extracting and structuring information from technical documents alongside native engineering formats.
Document extraction is part of Rine's product direction, but it is not currently a verified La Vinci Developer Preview capability.
Built for software serving engineering-heavy industries.
The underlying file problem appears in many different markets.
AEC
Drawing ingestion, visualization, export, technical-document workflows.
Manufacturing
Product and production file workflows.
Mechanical engineering
Engineering-data ingestion and transformation.
Aerospace & automotive
Complex technical-file infrastructure inside specialized software products.
Energy
Engineering drawings, technical assets, and system data.
Industrial software
File ingestion and engineering-data infrastructure inside automation and operational products.
What can I build today?
Have a workflow that doesn't fit neatly into the preview?
Some of the most useful Rine capabilities will come from real software products that depend on engineering files.
If the problem fits Rine's infrastructure model, we can evaluate it together before either side commits to a larger integration.
We're interested in working with teams that can bring:
Representative files
Realistic examples of the assets your product needs to handle.
Defined outputs
What your application actually needs extracted, transformed, rendered, or returned.
Success criteria
The accuracy, fidelity, diagnostics, and behavior required for the workflow to be useful.
Build the product. Let Rine handle the engineering-file layer.
Start with the Developer Preview or bring us the file problem your product needs solved.