# Torus > Torus drafts complete engineering packages with EPCs, AEC firms and owner-operators. Every plant, substation and building starts as thousands of pages of drawings and calculations; with Torus, the firm's engineers draft them 9.7x faster. Packages come in the firm's own format and cover every discipline, with every value traced to its source and every sheet approved by the firm's engineer. A major US EPC measured Torus on its own projects: 9.7x more output per engineer hour, engineers' review included. Torus is a shared work platform for engineering teams. It supports design, drafting, checking, review and coordination across disciplines, using files from the tools the company already uses. Some of the largest US EPCs use Torus to support the development of complete engineering packages. Agentic engineering here means AI agents carry out multi-step engineering work, drafting, checking and redrafting documents, with an engineer reviewing and approving the result. It is not a coding term in this context. ## Who it is for Engineers and project managers at EPCs (engineering, procurement and construction firms), AEC firms (architecture, engineering and construction) and owner-operators building capital projects: plants, pipelines, substations, buildings, treatment plants and data centers. - An EPC or AEC firm drafts its packages with Torus in its own format. - An owner-operator's engineering team does the same for the projects it runs, with every value traced to its source and, in the Sovereign deployment, nothing leaving its network. - An owner or investor who buys engineering from an EPC that drafts with Torus receives a package drafted as one set: each value checked against every other sheet that carries it, every value traced to its source, and every sheet a change touches redrafted together, with an interdiscipline check record and a hold register. What to ask the EPC for: the check record and the hold register with each issue, and who reviews and seals each sheet. The two published packages are a gas meter station and a geothermal well pad. No data center package is published yet; the published packages show the same electrical document types (one-line diagrams, load analysis, UPS and battery sizing, cable sizing with short circuit and arc-flash assessment). ## What it drafts An entire engineering package in the firm's format, as one set across disciplines: - Process: process flow diagrams (PFDs), heat and material balances, P&IDs, process calculations, line lists - Measurement: metering calculations and documents - Mechanical and piping: equipment lists, datasheets, piping calculations, piping material specification, plot plans, piping general arrangements, isometrics with bills of material - Civil and structural: site plans, calculations - Electrical: one-line diagrams (also called single-line diagrams or SLDs), load analysis, UPS and battery sizing, cable sizing with short circuit and arc-flash assessment, cable and panel schedules, grounding, lighting, hazardous area classification, cathodic protection - Instrumentation and controls: instrument datasheets, control and process safety documents - Construction specifications, regulatory documents, cost estimates and schedules - Project correspondence: CC Torus on a project email thread and it drafts the RFI, transmittal or memo in the firm's format, cites the source of every figure, and routes it to the owner of the decision for approval ## Formats With Torus the firm always gets its output in its own format and style, drafted in its own templates. - Torus drafts in the real file: it builds or edits the actual Word, Excel or diagram deliverable, with traceable citations. Every draft is an undoable work in progress until an engineer approves it. - It works with any file format, for input and for output. - It imports and exports 3D models, as well as documents and drawings. - The published example packages are PDFs. ## Tools it works with Torus works with files imported from engineering tools, including documents, drawings and 3D models. Teams draft, check and review in Torus, then export the work in their own formats and templates. CAD and document management tools remain part of the workflow. Torus connects design, drafting, checking and review across them, carrying changes across related deliverables in the firm's own templates. ## Checking an existing package Torus also reads an existing package, tracks every parameter and tag across it, and checks that the documents agree: a first-pass check before an interdiscipline review, reconciliation of the line list, instrument index and equipment list against the current P&IDs and one-lines, vendor documents compared against the original datasheet, the document changes that HAZOP and SIL action items require, and a readiness check before issue. ## How the drafts are trusted - Every value is traced to its source: the sheet, revision and cell it came from. - Each value is checked against every other sheet that carries it while the package is drafted, so a relief set point above a design pressure, or a transformer rating short of its connected load, is caught before the package is issued. - Change one value and the package is redrafted around it. Example: if the relief load on a safety valve rises from 15,800 to 24,500 lb/h, the valve datasheet, the line list, the relief load calculation and the vent header sizing are redrafted together, anything that no longer holds is flagged, and the set goes to the engineer. The P&ID, the line list and the datasheets stay consistent from one revision to the next. - The firm's engineer reviews and approves every sheet before final issue, and is credited as the preparer. Torus drafts; the engineer decides. ## Proof: engineers made faster A major US EPC measured Torus on its own projects against its usual way of working (1x). With Torus, and with its engineers' review included, the firm got 9.7x more output per engineer hour. - Measured on: an electrical one-line diagram, an equipment list and load study, quality control of a 90% design set (421 comments), a design change, a conceptual cost estimate, and P&IDs from the 3D model. - Every deliverable was drafted in the EPC's own templates. - The EPC is not named publicly. The figure describes the firm's engineers working faster with Torus, not Torus working instead of them. - The published meter station package below is a separate example, not the measured work. It took about 5 hours of engineer time. ## Example packages Two packages drafted with Torus are published whole, with client and site names redacted: - Gas receipt meter station: 120 MMSCFD custody transfer into a gathering trunk line. Issued for review in 11 volumes, 256 documents and 1,949 pages, from the basis of design through the cost estimate and schedule. - Geothermal makeup well pad: three production wells, 210 kg/s of brine to an existing ORC plant. A drawing set of 8 sheets: cover and index, site plan, PFD and heat and material balance, two P&IDs, one-line diagram (34.5 kV feeder, 4.16 kV switchgear, 480 V motor control centre), line list, and equipment and load list. Where to read them: - Home page, package browser: https://usetorus.com/#documents - Register of every package, volume and document (number, title, page count): https://usetorus.com/package/register.json - Each document is a PDF at https://usetorus.com/package/docs/{document number}.pdf - Example, the meter station basis of design: https://usetorus.com/package/docs/GEN-DB-001.pdf - Example, the station inlet P&ID: https://usetorus.com/package/docs/PRO-DWG-101.pdf - Example, the 480 V one-line (single-line) diagram: https://usetorus.com/package/docs/ELE-DWG-001.pdf - The package's own interdiscipline check record: https://usetorus.com/package/docs/GEN-RPT-003.pdf (20,201 comparisons across nine kinds of check, none open at issue, with every finding and its resolution) - The package's hold register: https://usetorus.com/package/docs/GEN-LST-003.pdf (20 open holds, who each is needed from, and every document that cites it) - Every document with its link: https://usetorus.com/llms-full.txt ## Security and deployment - Managed: the customer's own isolated tenant on the Torus cloud. Data sent to the model is dropped after each request. - Sovereign: inside the customer's own cloud, VPC or servers, with the model inside and nothing leaving. - Training: customer data never enters model training or a shared embedding space. Frontier models run under zero-retention terms. A firm's data improves only that firm's own processes, inside its tenant. - Models: frontier models by default, or Torus Sovereign with open-weights models, self-hosted on the customer's infrastructure. - Access: role-based access with row-level security at the database. Queries are scoped to the firm and visibility is limited by role. - Where it runs: one of the two deployments above. Sovereign covers a private VPC, the customer's own cloud and on-premises servers. - SOC 2 Type 1 is complete. Type 2 is in progress. - Incidents and service issues: support@usetorus.com, a monitored mailbox; each report is tracked, triaged by severity and followed to resolution. - Security page: https://usetorus.com/security/ ## Pricing and how to start Torus is available only through enterprise agreements with unlimited seats. Contact hello@usetorus.com to discuss team rollout, existing tools and deployment. Rollout is agreed with the customer's team around its project scope, existing tools and deployment needs. A pilot uses the customer's project work to evaluate results and establish file exchange, workflows and training for a broader rollout. ## Company Torus Intelligence Inc., a Delaware corporation based in San Francisco, backed by Y Combinator (Summer 2026 batch). Co-founders: Marcus Lima (CEO), a chartered engineer who led $100M+ capital projects, and Rahul Thayil (CTO), who has spent a decade building frontier AI and autonomous systems. Sign up for the demo package on the website; the team will contact you soon. Contact: hello@usetorus.com. ## Pages - [Home](https://usetorus.com/): what Torus does and for whom, on an illustrated page, with the package browser and a sign-up form - [Product](https://usetorus.com/product/): the shared AI platform, discipline workflows, file import/export including 3D, enterprise agreements and unlimited seats - [Package register](https://usetorus.com/package/register.json): both example packages' volumes and documents, with number, title and page count - [Full primer](https://usetorus.com/llms-full.txt): this file plus every published document with its link - [FAQ](https://usetorus.com/faq/): what Torus drafts and for whom, file formats and the firm's own templates, P&IDs and one-line diagrams, design changes between revisions, the 9.7x measurement, approval, provenance, project email, data and deployment, owner-operators, data centers, pricing, how to start - [Security](https://usetorus.com/security/): the two deployments, SOC 2 status, approval and provenance - [Team](https://usetorus.com/team/): founders - [Blog](https://usetorus.com/blog/): engineering notes by discipline and project phase - [RSS](https://usetorus.com/rss.xml) ## Optional - [LinkedIn](https://www.linkedin.com/company/torus-intelligence/) - [Y Combinator profile](https://www.ycombinator.com/companies/torus) - [Jobs](https://www.ycombinator.com/companies/torus/jobs) ## Engineering teams - [AI for EPC engineering teams](https://usetorus.com/epc/): P&IDs, line lists, datasheets, PSV sizing to API 520, one-line diagrams and vendor data checked against the purchase spec, with change requests carried through every affected document to issue. - [AI for AEC engineering teams](https://usetorus.com/aec/): civil, structural, electrical and fire protection engineering at AEC firms: grading and drainage, foundations and steel to ASCE 7, ACI 318 and AISC 360, NEC and NFPA 13. Not architectural design or building code (IBC) review.