Software for engineering teams and industrial companies
Steyer Engineering builds software for engineering teams and industrial companies: ERP and business software, web platforms and portals with payments, AI assistants and chatbots, CAD and 3D tools, and the links between systems. The company is certified to ISO 9001:2015. Headquarters are in Taraz, administration is in Almaty. We write in English, German, Russian, and Chinese.
What gets built
On the business side: ERP with quotes, invoices, dunning, DATEV export and EU e-invoicing (EN 16931), plus HR, time tracking, projects, CRM and inventory, with email, calendar, documents and chat in the same system. It runs on your own server if you prefer, with more than one tenant, access by role, two-factor login, and GDPR where that applies. On the web: customer portals and admin back offices, checkout with card and crypto payments, and identity checks (KYC). Websites and web design are done by our brand Steyer Studio (steyer.studio). From the engineering side: STEP, JT, and GLTF viewers in the browser, native CAD decoders, and desktop applications. The stack is React and Next.js, TypeScript, Node.js and Python, PostgreSQL and Docker, plus Three.js and WebGL, Electron, and OCCT or HOOPS.
AI assistants and chatbots
Chatbots for Telegram and WhatsApp, built on large language models, that answer questions, qualify leads, and walk new customers through onboarding in several languages. Your team sees each conversation in the CRM and can take it over. Filters keep personal data and credentials out of the answers. Where data must stay in-house, the AI runs on your own server: email drafts and translations, document summaries, and reading receipts with OCR.
How a build runs
We start from your process and write the specification with your team. You see working software in steps, not only at the end. Requirements, versions, tests, and releases are written down under the ISO 9001:2015 system. You receive the source, the documents, and a build your own people can change.
Links between systems
Scripts, PDF and other documents, data export, ETL, and APIs connect what you already run: payments, email, messaging, CRM, spreadsheets, and CAD or PLM. Releases go out through an automated pipeline with health checks and a rollback to the last good version. The point is less retyping between those tools.
Who it is for
The software is for engineering and production teams in automotive, aerospace, rail, and other manufacturing. Site work for OEMs and tier-1 suppliers in Europe and Central Asia is why the tools follow the limits of a production plant: a portal, an ERP module, a chatbot, a 3D view, or a small automation job.
Frequently asked questions
What kind of software do you build?
Business software such as ERP with finance, HR, projects, CRM and inventory; web platforms and customer portals with online payments and identity checks; AI chatbots and AI that runs on your own server; integrations and automated workflows; and engineering tools such as STEP, JT, and GLTF viewers, native CAD decoders, and desktop apps.
Which technologies do you use?
React and Next.js with TypeScript and Tailwind, Node.js and Python on the server, PostgreSQL, and Docker for deployment. Three.js and WebGL, Electron, and OCCT or HOOPS for CAD data; large language models for AI functions. Integrations use APIs, webhooks, scripts, and data export between the systems you already run.
How does a software project run?
We write the specification with your team, starting from your process, and you see working software in steps, not only at the end. Requirements, versions, tests, and releases are documented under ISO 9001:2015.
Do we receive the source code?
Yes. You receive the source code, the documents, and a build your own people can change, including deployment notes and a short description of how to change a user or a report.
What you get
- ERP with finance, HR, projects, CRM and inventory
- Web platforms and portals with payments and KYC
- AI chatbots and AI on your own server
- 3D in the browser and CAD decoders (Three.js, OCCT, HOOPS)
- PDFs, scripts, and APIs between your systems
- Source code and the documents that go with it
Write what you need built. We will answer with a scope.