Bring us the engineering-file problem.
Building software or AI around CAD, engineering files, drawings, or technical documents? Tell us what your product needs to do with those files.
For product teams, developers, and technical leaders at software and AI companies.Looking for Project La Vinci?
Active development on the general-purpose CAD conversion path is paused while we refocus on customer workflows. Read the full technical retrospective and corpus findings.
Building something that depends on engineering files?
Tell us about the workflow below. This includes teams evaluating an integration, working with unsupported formats, or dealing with extraction, conversion, normalization, rendering, or technical-document problems.
Tell us what you're building.
We review every workflow ourselves. If it looks like a good fit for Rine, we'll follow up to understand the technical requirements and agree on the smallest useful next step.
Some workflows won't fit Rine's currently verified capabilities yet.
That doesn't automatically make them irrelevant. For suitable engineering-file infrastructure problems, we may work with a company as a design partner.
Representative assets
You provide realistic examples of the files or documents involved.
Required output
We establish exactly what your product needs Rine to return or preserve.
Success criteria
We agree on what useful means — accuracy, fidelity, diagnostics, performance, or another measurable requirement.
Technical evaluation
Rine tests the workflow against that standard.
Integration
If the capability proves useful, we can explore how Rine fits into your stack and what a commercial relationship should look like.
Rine only represents formats and workflows as supported once they have actually been built and verified. If your workflow involves something outside our current verified capabilities, we'll treat it as a problem to evaluate — not as something we already support.
Building around engineering files?
Tell us what the file layer is making difficult.