Abstract Byte
ASCII A B S T R A C T — one byte per row

Lisbon, Portugal — AI · Robotics · Cloud

We engineer for the problem you haven’t hit yet.

Abstract Byte takes teams from a hard problem to a running system — and builds it to hold when the problem changes.

What we do

Three fields, one engineering practice.

Artificial intelligence

Models in production, not notebooks.

Retrieval, agents, and decision systems — with the evaluation harness and guardrails that keep them honest once real users arrive.

  • Retrieval and agent architectures
  • Evaluation and regression suites
  • Fine-tuning and model selection

Robotics

Machines that read a real environment.

Perception, control, and integration work on hardware that has to behave the same on the factory floor as it did on the bench.

  • Perception and sensor fusion
  • ROS 2 integration and control
  • Edge inference and telemetry

Cloud

Architecture that scales with the bill in mind.

Event pipelines, Kubernetes, and infrastructure as code — designed so your own team can run it after we leave.

  • Platform and Kubernetes design
  • Data and event pipelines
  • Cost, observability, and CI/CD

Where it gets interesting

Most of our work lives on the seams.

Plenty of firms do one of these three well. The hard problems — and the durable advantages — sit where two of them meet.

AI × Robotics

Embodied autonomy

Machines that decide on their own sensor data, at the edge, without a round trip to a datacentre.

Robotics × Cloud

Fleet operations

One robot is a project. A hundred is a distributed system. We build for the second case from day one.

Cloud × AI

Inference at scale

Serving models to production traffic, with latency, unit cost, and rollback all accounted for.

Engagements

Three ways to bring us in.

Advisory

Architecture reviews, technical due diligence, and the roadmap that comes out of them. For teams deciding what to build before they build it.

Weeks, not quarters

Delivery

End-to-end build. We scope the system, ship it, and hand over something your engineers can extend without calling us.

Fixed scope or retainer

Embedded

Our engineers inside your team — your repo, your standups, your on-call rotation — for as long as the problem needs them.

Monthly, renewable

How we work

Four stages, in this order, every time.

01

Scope

One week. We map the problem, the data, and the constraint that actually binds — which is rarely the one in the brief.

02

Prototype

A working thin slice in front of real users or real hardware, early enough that changing direction is still cheap.

03

Harden

Tests, observability, cost controls, and every failure mode written down and handled rather than discovered in production.

04

Hand over

Documentation, runbooks, and a working session with your team. The goal is a system that no longer needs us.

Founded in Portugal.
Built for the world.

Lisbon  38.7223° N, 9.1393° W
Working with teams across Europe and North America
Contracts in EUR or USD · EU-based, GDPR by default

Contact

Tell us what you’re building.

Send the problem, not the RFP. A paragraph about what’s stuck is enough to start a useful conversation.

anunuparov@abstractbyte.dev

Good first messages
“We have a model that works locally and falls over at 200 requests a second.”
“We are deploying 40 machines next year and have no fleet story.”
“Our cloud bill tripled and nobody can say why.”