Engineering acrosssoftware, siliconand steel.
Accron is an engineering studio run by Arun Kumar. We build web platforms and backend systems, write automotive Android software down to the platform layer, and take hardware from schematic to machined, printed part.
- Engineering disciplines
- 7Engineering disciplines
- Projects delivered
- 25+Projects delivered
- Years hands-on
- 10+Years hands-on
- Continents served
- 3Continents served
What we do
Seven disciplines, one engineering team.
Most studios stop at the browser. We carry a product from the interface through the API, into the firmware, and out the other side as a physical part.
The Forge
One part, three disciplines, no hand-off.
Scroll through a real workflow: the model that carries the tolerances, the tool path that cuts it, and the system it ends up inside. Same team, same file, no translation loss in between.
01 / Model
It starts as a sketch.
A constrained 2D profile, extruded, drilled and chamfered. Every feature carries the tolerance and the material it will be cut from, because the model is the manufacturing instruction, not a picture of one.
02 / Machine
Then the tool path takes over.
Roughing passes at depth, a finishing contour, and stock that only exists where the part does not. We program the path, the fixturing and the work offsets, then check them against the machine that will actually run them.
03 / Integrate
Machined parts become a system.
Cells, busbars, a BMS and the enclosure that holds them square. This is where the disciplines meet: the firmware that balances the pack runs on a board that fits a housing we cut ourselves.
Selected work
Things we actually built.
Platform-level automotive Android, realtime voice systems, factory operations software and machines that make their own filament.
How we work
Predictable delivery, no theatre.
The same four steps whether it is a marketing site or an instrument cluster.
- 01
Scope
We work out what actually needs building and what does not. You get a written scope with milestones, deliverables and a fixed cost before anything starts.
- 02
Prototype
The riskiest part gets built first. That means the hardware bring-up, the tricky integration, the interaction nobody is sure about. Risk surfaces in week one, not month three.
- 03
Build
Delivery in reviewable increments. Web work lands on preview URLs; firmware and mechanical work ships as testable builds and physical samples.
- 04
Hand over
Source, documentation, build instructions and deployment access are yours. No lock-in, no dependency on us to keep the lights on.
Have something that needs building?
Tell us what you are working on. If it is a fit we will come back with scope, timeline and cost. If it is not, we will say so and point you somewhere better.