Skip to content
AtaForge
[Company]

A robotics company with one obsession

Autonomous machines for physical work — mechanics, autonomy and fleet software built on one engineering core

  • #Robotics
  • #One-platform
  • #Construction-first
  • #Delaware-and-Malta
  • #Evidence-first
[01]Position

A robotics company, not a studio

AtaForge builds autonomous machines for physical work and the platform that runs them — autonomy, a deterministic safety architecture and fleet software, built once and carried by every machine. Construction is the first application. The other sectors we name stay labelled exploration until they earn more.

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.

First product

M200 Construction Mule

Autonomous material transport for construction sites: ~200 kg payload, waypoint navigation with follow-me mode in the next phase, all-weather duty, and a safety system designed for working near people. The only program with an engineering pack behind it.

First product · software complete, prototype build starting

Open →
Research program

ACR-1 Quadruped

A four-legged research platform for the terrain wheels cannot handle — stairs, debris, unfinished floors. Simulation-first by design: no physical build until measured milestones are passed.

Research · simulation only

Open →
Exploration

Exploration · concept stage — not products, not an announced roadmap

Material-placing manipulator — construction · Autonomous water taxi — marine · Field platform — agriculture · Search and assist — disaster response. Each would reuse the same autonomy, safety and fleet layers — and each still has to earn its own evidence before it becomes a program.

[02]Principles

How we decide what to build

[01]

Hardware and software, one team

A robot whose software is written somewhere else is a robot that fights its own firmware. Mechanical, embedded, autonomy and fleet engineering sit on the same program.

[02]

AI where it earns its place

We use models when they outperform a rule, and rules when they outperform a model. Nothing an AI outputs ever reaches the stop decision — that chain is deterministic by design.

[03]

Built for audit, not for demo

Traceability, documentation and an append-only decision log are part of the build from week one, because a machine that works near people is an accountable system.

[04]

Evidence before claims

Capabilities are demonstrated in simulation, then proven physically, then claimed — in that order. Every number we publish is labelled by where it came from.

[03]Capability core

One core, many machines

[01]

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.

[02]

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.

[03]

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.

[04]

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.

[04]Delivery

How the program advances

  1. [01]

    Simulation

    Mission logic, fleet coordination and tasking validated across thousands of simulation runs — complete, and labelled simulation until the yard says otherwise.

  2. [02]

    Prototype build

    The first physical M200: chassis, drivetrain, sensors and the safety chain. Procurement and detailed design under way; no hardware built yet.

  3. [03]

    Yard validation

    A fenced test program before any robot works near people. The safety chain is proven before the motors get power.

  4. [04]

    Supervised pilots

    Partner sites, supervised and measured against targets signed before the trial starts. Robots rented as outcomes, never sold as machines.

[05]People & place
Süleyman Kasıkcı, founder of AtaForge

Süleyman Kasıkcı

Founder

One founder, an AI-augmented engineering organization

AtaForge is founder-led and runs a documentation-first, evidence-driven engineering process in which AI agents do a large share of the engineering work under human direction. That process produced a complete, release-tagged software platform — and it is part of what the company is.

AtaForge Inc. is registered in Dover, Delaware, with AtaForge Europe Ltd. in Malta — one robotics engineering organization, working worldwide and on site wherever a yard or a construction site requires it.

Platform under every machine
01Platform under every machine
Legal entities, one organization
02Legal entities, one organization
Reply to every enquiry
24hReply to every enquiry

Talk to the people building it

Send the site, the problem or the question. If it fits the M200 program, a pilot or a domain we are exploring, we will say exactly how we would approach it — and if it does not, we will say so.