Our product, no equivalent on the market

A STEP assembly goes in. A full drawing package comes out.

Partnership terms

32Studio is a web tool for mechanical engineering. A STEP assembly from any CAD goes in. The bill of materials, the assembly drawing and a separate sheet for every part come out, in DXF and PDF.

A real object, a production hangar frame, came out as 340+ sheets in 47 minutes. See the case

One run on a public test assembly, timer on screen, no cuts. Captions burned in, sound optional. Test assembly: a public open-source assembly. Not a customer part. The title block is blanked on purpose.

3D model of the steel frame of a production hangar in a CAD viewport: lattice columns, roof trusses and purlins as a wireframe

Real object

A production hangar frame, every member on its own sheet.

Editable sheets
340+DXF and PDF, one per member
32Studio, the whole frame
47minA design engineer by hand: 2 months
Errors
0In 340+ sheets

Compared

There is no direct equivalent. The two closest tools are below, feature by feature.

Feature32StudioAutodesk Fusion, automated drawingsDraftAid
A STEP assembly from any CAD goes inYesYesAfter import into FusionYesSTEP, through a SolidWorks or Inventor plugin
Assembly drawing and bill of materialsYesYesParts list and balloonsNoParts; assemblies in beta
Finished sheets, nothing to tidy by handYesNoTidied up in Fusion afterNoFinished in SolidWorks or Inventor
No CAD seat, nothing to installYesNoThe Fusion app, on subscriptionNoA plugin inside SolidWorks or Inventor
Editable DXF and PDF outYesYesPDF, DWG, DXFYesNative drawings, DWG, DXF, PDF
Your model is deleted after the runYesNoDesigns live in Autodesk's cloudNot publishedNot published
What it costsNothing, for a partnerA Fusion subscriptionAn annual license by drawing volume

Facts about the other two come from their own pages and published interviews.

Partnership

We are looking for one partner to teach 32Studio your drafting standard. One engineer is enough.

It can be you alone or your whole design department. You show us how your sheets should look, we make the engine draw that way, and you keep the result at no charge. That is why the letter came to you.

How it goes

  1. 01

    Send one assembly

    A STEP file and the finished 2D drawings made for it.

  2. 02

    We run it through 32Studio

    The service draws the whole assembly, and the sheets come back to you.

  3. 03

    You mark what is wrong

    A few rounds like this, until the sheets match your standard.

Your file
  • Full NDA, signed first
  • Seen by three people
  • Deleted when the rounds end
  • A full NDA, on your paper if you prefer, signed before the assembly is sent.
  • One assembly you are free to share, sent after the call, only if you go ahead.
  • The storage location is named in the NDA. Opened by three people on the product team.
  • Used only to make the engine draw to your standard. Never a demo or a sample without your written OK.
  • Deleted when the rounds end, or earlier when you say so, confirmed in writing.
  • Files you open in the tool yourself go to the engine, whose location the NDA also names, and are removed after the run.

If your compliance person wants this in writing before the call, write to ravil@32studio.io.

What you get

Your own version of 32Studio, at no charge.

  • Sheets in your standard: projection, units, title block, notes
  • For you alone, or for your whole team
  • Other terms are open to discussion

Hours saved a month

56h

About 7 working days of a design engineer, back every month.

500
By hand58 h 20 min
In 32Studio2 h 22 min

One sheet takes 7 min by hand and 17 s in 32Studio. Multiply the hours by what a drafting hour costs you.

Who we are

The tool started as a fix for our own drafting backlog.

32Studio is built by six people: design engineers, programmers and a mathematician who came from mechanical design and drafting. A version for your drafting standard does not exist yet, which is why we write to people who draw to it every day. The contracting party and its registry details are named in the NDA, before any assembly is sent.

Leads the project. Writes to you and runs the review rounds.

Ravil Fayrushin

Project lead

Machine building since 2007 · MBA · 2 registered software programs

Leads the research. Builds the CAD tools and the neural network that reads data from drawings.

A. Vinogradov

Research lead

Full stack: React, Python, GraphQL · Master’s in engineering

Shapes the method behind the geometry: supercomputer modelling of complex objects.

A. Efimova

Methodologist

Applied mathematics · Postgraduate research · Scopus H-index 3

Wrote the dimensioning and section-view algorithms in 32Studio.

D. Shatalov

Programmer

14 years as a design engineer, aerospace and defence · Master’s in mechanical engineering

Develops the core modules of 32Studio.

D. Gorokhov

Software engineer

10+ years in CAD · 3+ years of Python in industrial systems

Tests and verifies the prototype before it reaches you.

S. Khitrin

Test engineer

1C developer · Lean-manufacturing coach · Production director

Reply

Reply to our email, or pick a slot for a call below.

Or write to ravil@32studio.io, the same domain as this page. If a call is easier, pick a slot: screen share, no slides, we run the test assembly live and you ask what you want.

The calendar below is Cal.com's. It asks for a name and an email.