
ENGENTIC integrates AI into every aspect of the engineering process. Simultaneously solve and document any problem or build a complete system from requirements documents.
Create an AccountEngentic is a simultaneous analysis and documentation platform. Its documents contain both text, headers, and normal document components as well as equations, plots, and everything needed to solve and document a problem.
Text, equations and plots in one page that solves as you write.
Folders that hold and organize your documents, datasets and part trees.
A system broken down into subsystems and parts, with a document for each.
Tables of data that your documents can read and calculate from.
A document is a list of blocks that solve in order. The main menu on the document is a section of hexagons. When clicked they open submenus that let you add items to the document or edit properties of the document.
Add blocks, go home, set units and constants, connect CAD, and save.
The block types you can add: equations, plots, loops, sliders, text, images and more.
Equations are written and solved in the page, with units. The result sits next to the formula.
Text and headers sit between the equations, so the calculation explains itself.
Open a workspace to see how Engentic is used.
Our documentation workspace provides a users guide that walks users through all facets of ENGENTIC.
The homework workspace provides hundreds of examples in subjects such as physics, statics, dynamics, and mechanics of materials.
The examples workspace provides a few examples designed to get the user started working with ENGENTIC and using part trees.
Workspaces hold your documents, datasets, part trees and images, and can contain other workspaces.
Go home, open your profile and teams, set units and constants, and connect CAD.
Add opens the items you can create here: documents, datasets, part trees, images and workspaces.
The location trail shows where you are in the tree of workspaces.
The documents and folders in the current workspace, with when each was created and last changed.
AI is used in all 4 facets of the platform - documents, workspaces, datasets, and part trees. In workspaces, it mainly answers questions the user may have. In datasets, it can guide and assist the user in parsing data. However, the main use cases for AI are in documents and part trees.
The chat assistant works in three modes, so you choose how much it is allowed to touch.
The same three modes apply, and the assistant can also build a whole tree from your requirements documents.
Describe a problem in plain words. Build mode works it out in three steps and adds the result to your document as ordinary blocks you can read and edit. Here is one example.
Size a timber beam. It is 200 mm wide and simply supported over 6 m. It carries 12 kN/m along the whole span and a 20 kN point load 2 m from the left support. Keep bending stress under 12 MPa and shear stress under 1 MPa. Pick the depth in 25 mm steps.
It reads your prompt together with the document and states the problem: what is given and what has to be found. You see this in the chat, so you know how it read the request.
Design the depth of a rectangular timber beam, 200 mm wide, simply supported over a 6 m span. Loads: 12 kN/m over the full span and a 20 kN point load 2 m from the left support. Allowable stresses: 12 MPa in bending and 1 MPa in shear. Find the support reactions, the maximum bending moment and the smallest depth that satisfies bending, round it up to a 25 mm step, and check bending and shear for that depth.
It writes only the equations. The platform's unit-aware solver calculates every one of them. If an equation has an error, the error is sent back so the model can correct it. The numbers come from the solver, not from the model.
With the solved equations in hand, it writes the headers, text and symbolic formulas around them. Each solved equation is placed once, with the value the solver found.
The beam is governed by bending, and the bending moment is largest where the shear force passes through zero. That happens 2.44 m from the left support, where the moment reaches 75.85 kN·m. Dividing by the allowable stress gives the section modulus the beam needs, and from it the smallest depth for a 200 mm width.
σ = M / S
A 450 mm depth passes both checks: 11.24 MPa in bending against 12 MPa allowed, and 0.82 MPa in shear against 1 MPa.
Build mode adds equations, text, headers and symbolic formulas. Plots, images, sliders and loops come from the Add menu.
NASA Goddard has described a vision called Text-to-Spaceship: plain-language requirements flowing through AI-accessible design, analysis, and manufacturing tools to cut mission development time. ENGENTIC is building the engineering platform for that workflow.
Plain-language goals and constraints, captured as requirements in the part tree.
The assistant drafts the calculations, documents and plots that answer them.
A deterministic, unit-aware solver checks every number against the requirements.
Verified parameters flow into Onshape and Fusion models, and changes flow back.
ENGENTIC is an independent project and is not affiliated with or endorsed by NASA.
In a part tree, Build mode starts from your requirements documents. It lays out the systems and parts, writes down how it read your requirements, and then builds a calculation document for each part. Here is one example.
The footbridge is a steel truss bridge spanning 12 m. Two identical trusses, each made of a top chord, a bottom chord and diagonal members, carry a timber deck between them.
Read the requirements documents and build the system in question.
The main coordinator reads your requirements documents in full, including the requirements you flagged. It decides which systems and parts sit directly beneath the top. Anything already in your tree is kept and filled in around, not replaced.
Every system and part gets a design document: where it sits, which requirements reach it, what it needs from its neighbours, the values the documents state, and the design intent. A requirement that doesn't apply to a part isn't passed to it. You can read these to see how your requirements were interpreted, and stop here before any part is built.
Every system gets its own coordinator. It reads the design document one level above it and its own requirements documents, then decides the structure beneath it and writes its own design document. This continues down the tree.
The Deck gets its own coordinator in the same way.
A part agent reads the part's design document and works out the design as equations. The platform's solver calculates them and sends back errors and failed checks to be fixed. It then writes the part's document, placing each solved equation by number, so the text cannot change a result.
The tree and the design documents are written first. You can stop there and read them before any part document is built.
ENGENTIC equations can be sent to Onshape and to Fusion 360 to drive CAD models and those models can be read back into ENGENTIC


ENGENTIC licences are free for students and for those learning the platform.
Start today with your own work or by jumping into group projects.