AT DevLab

Machine translation from Italian, not yet reviewed.

Independent software house

From the Commodore 64 to today's apps.

We are computer engineers. We wrote our first lines of code as kids and opened our first PC with a screwdriver. Today we build apps for people on the road, for people who have lost a memory, for first responders and for investors.

About us

Over thirty years of curiosity, then the craft.

We weren't born in an incubator. We grew up taking things apart to see how they work, and the urge to do it never went away.

  1. Late '80s

    READY.

    A Commodore 64, games loaded from cassette and the first lines of BASIC copied from magazines. Changing a single number was enough to make something different happen.

  2. Early '90s

    The Logo turtle

    FORWARD, RIGHT, REPEAT: the first language that drew. That's where we learned the most important rule of the craft: a computer does exactly what you tell it, not what you mean.

  3. Late '90s

    The screwdriver, and nights on IRC

    We built PCs for ourselves, then for friends and family, then for anyone whose machine was broken. The answers the manuals didn't give were on IRC, asking people who knew more.

  4. High school

    Self-taught, at night

    Networks, Visual Basic, C++, the first databases. Linux from the Red Hat 6.1 CD, and BeOS because it looked like the future. We took part in the very first editions of Linux Day: free software taught us to share, and not to trust what can't be verified.

  5. Early 2000s

    When a disk stops spinning

    Virus removal and data recovery from damaged disks: theses, family photos, a shop's accounts. Then smartphones arrived, and we repaired those too. That's where we learned how much a file weighs for the person who loses it.

  6. Networks and security

    Looking inside systems

    Cisco certification in networking, and forensic analysis with the field's Linux distributions, such as Kali. Knowing how a system is attacked is the best way to build one that holds.

  7. The degree, then

    Software where failure isn't an option

    As computer engineers, we spent years leading development teams in the military sector. Strict requirements, tests without shortcuts, systems that must work the first time. That method stayed with us.

  8. And finance

    Banking, Stock Markets and Insurance

    Alongside engineering, a degree in finance specialising in Banking, Stock Markets and Insurance: markets, instruments, risk management. That's where HQMI comes from, combining mathematical models with specific training in the markets.

  9. Away from the keyboard

    Backpacks and the Red Cross

    Road trips and backpacking, and years as a tour leader for a travel agency, bringing a group to its destination. Then volunteering with the Italian Red Cross. Pinny and our tools for first responders come from there: we lived them before we coded them.

  10. Today

    AT DevLab

    The same rigour, put at everyone's service. We build our own products, small and precise, for real problems of everyday life.

What we do

Five projects, one idea: being there when it matters.

Two are being tested with their first users. Three are in development, and we talk about them with the caution they deserve.

In testing

Pinny

Testing on Google Play

Add your stops, Pinny finds the best order. An open pharmacy, a fuel station, a toilet for the kids: one tap away, on Android Auto too. No account, your trips stay on your phone.

Discover Pinny

Support: [email protected]

MediaSalvage AI

In testing, online soon

Damaged photos, videos and archives, repaired with artificial intelligence. Upload the file, see the preview, pay only if it was recovered. It's our old craft, done with today's tools.

Soon at mediasalvage.ai

Reference for data in the cloud: ISO/IEC 27018

Support: [email protected]

In development

HQMI

In development

HQMI is a new index, designed by us and built specifically for this project: it is not an existing market indicator. Our models use it to study the behaviour of stocks, ETFs and gold and estimate where the market may go. Clear numbers, stated risk, no promise of easy gains.

Behind it is a degree in finance, specialising in Banking, Stock Markets and Insurance, as well as the one in computer engineering.

An analysis tool, not financial advice. No model predicts the market with certainty.

Epileptic seizure prediction

In research

Software that studies the body's signals to recognise a coming seizure in advance, and give the person who has it, and those nearby, a few more minutes to get safe.

A research project. It is not a medical device and does not replace a doctor's advice.

Tools for first responders

In development

An app for people who respond to emergencies: clear information, few screens, no distractions. It works even when the signal is weak, because that's where it's needed.

We are designing it with people who do rescue work in the field.

Privacy and security

Privacy by design, in all our software.

Data protection isn't added at the end: we decide it before writing the first line. Every product collects only what it needs, keeps it as briefly as possible and, when it can, leaves it on your device.

GDPR · ISO 31700-1 · ISO/IEC 27701

Data processing

Data protection by design and by default (GDPR art. 25), with the international standard on privacy by design for consumer products and the one on personal information management. Minimisation, clear notices, deletion on request.

ISO/IEC 27001 · 27002 · NIST CSF 2.0 · NIS2

Information security

We use as our reference the controls of the ISO standards, the NIST Cybersecurity Framework and the risk-management measures of the European NIS2 directive: access management, encryption, secrets never in the code, logs without personal data, and penetration testing.

NIST SSDF · OWASP · ISO/IEC 27034 · ISO/IEC 25010

Secure, quality development

NIST's Secure Software Development Framework (SP 800-218), the OWASP requirements, the ISO standard on application security and the software quality model: code review, automatic checks on every change and dependency scanning for known vulnerabilities.

ISO/IEC 42001 · AI Act

Artificial intelligence

Where we use AI we take as our reference the standard for artificial intelligence management systems and the European AI Act: we say what it does and what it can't do, and the result always remains verifiable by a person.

ISO and IEC standards and NIST frameworks are the reference we work with, not certifications issued by a third party. When we obtain one, you'll find it here with the certificate number.

How we work

Three rules we don't negotiate.

Few products, done well

We'd rather have an app that does one thing and always does it, than ten half-finished features. No ads, no profiling, no accounts unless they're needed.

We measure, we don't promise

Every feature is tried on real cases before it ships. If a number ends up on the site, it's because we measured it.

Simple under pressure

We design for people who are in a hurry, tired or worried. If you need a manual to use the app, we got it wrong.

Got an idea, a problem or a question?

Write to us. We answer ourselves, not an automatic form.