A robotics company with one obsession
Autonomous machines for physical work — mechanics, autonomy and fleet software built on one engineering core
- #Deep-tech
- #Applied-AI
- #Hardware-and-software
- #Dover-Delaware
- #Worldwide-delivery
We stopped being a general software studio
AtaForge builds machines that work on a factory floor, software that clinicians rely on during a shift, and platforms that teach students who all learn at different speeds. Those are engineering problems, not website problems — so we structured the company around them.
Everything we ship is production work: a robot that has to run its shift, a safety chain that has to satisfy a certification body, a fleet system an owner trusts with their site. We would rather own one hard domain completely than quote for everything.
M200 Construction Mule
An autonomous material-transport robot for construction sites: ~200 kg payload, tasked in plain language, coordinated as a fleet, built around a safety architecture where no AI output can reach the stop decision.
Software complete · prototype build starting
Open →ACR-1 Quadruped platform
A four-legged platform for the ground wheels cannot serve — stairs, debris, unfinished floors. Simulation-first by design: no physical build until measured milestones pass.
Research · simulation only
Open →Domains we study — not products, not an announced roadmap
Agricultural drones · Unmanned marine vehicles · Other field robotics. Each would reuse the same autonomy, safety and fleet layers — and each still has to earn its own evidence before it becomes a program.
How we decide what to build
Hardware and software, one team
A robot written for by a separate software vendor is a robot that fights its own firmware. Mechanical, embedded, model, and application engineers sit on the same project.
AI where it earns its place
We use models when they outperform a rule, and rules when they outperform a model. Every AI decision in a clinical or safety context stays explainable and reviewable.
Built for audit, not for demo
Traceability, access control, and documentation are part of the build from week one, because robots, patient data, and student data are all accountable systems.
You own everything
Source code, CAD, schematics, trained weights, and infrastructure configuration are handed over in full. No lock-in, no rented IP.
One core, many machines
Autonomy & perception
Mapping, localisation, obstacle handling and task planning that run on the machine itself — evaluated in simulation against thousands of runs before any hardware moves.
Safety architecture
An independent, hardware-level stop chain that never depends on AI. People always have right of way; the certification path is designed in from day one, not bolted on.
Fleet & operations software
Task allocation across many robots, live monitoring, offline-tolerant field apps and automatic daily reports — the layer that makes a robot useful to a business.
Mechanics & embedded systems
Parametric mechanical design, drivetrain and power architecture, and certifiable embedded control — the physical half, engineered by the same team as the software.
Every phase ends with something you can inspect
- [01]
Technical discovery
Two weeks on site and in the data. We map the process, the constraints, the regulatory surface, and the number that has to move.
- [02]
Prototype
A moving machine, a working model, or a clickable system on real data — early enough that changing direction is still cheap.
- [03]
Engineer to production
Hardening, integration, safety and compliance work, test coverage, and the documentation your auditors and operators will ask for.
- [04]
Deploy & operate
Rollout, operator training, telemetry, and a support agreement — with full source, schematics, and weights handed over to you.
Süleyman Kasıkcı
Founder
Small senior team, deliberately
AtaForge is run by engineers who have shipped hardware, regulated software, and consumer-scale platforms. Projects are staffed with senior people from the first day — there is no layer of account management between you and the person writing the firmware or training the model.
The company is registered in Dover, Delaware, and works with clients worldwide: remote by default, on site where a machine, a yard, or a construction site requires it.
- Focus domain
- 01Focus domain
- Response time
- 24hResponse time
- IP handover
- 100%IP handover
Work with the team, not with a pipeline
Send the problem. If it is something our robots or our engineering can solve, we will tell you exactly how we would approach it — and if it is not, we will say so.