Skip to main content
SuquiaBytes
Español Contact

Product studio · Córdoba, Argentina

We build software products end to end

Two engineers. We design, build and ship mobile, backend and AI products. We started with our own.

Let's talk

We work with clients in Argentina and abroad.

Our products

We have no wall of client logos. We have our own products: we designed them, we built them, we maintain them. That is considerably harder to fake.

Orisen

In active development

AI-powered assistive technology for blind people

  • Hardware
  • AI
  • Mobile
  • Cloud

The problem

Mobility aids detect obstacles, but they do not describe the environment. Orisen adds AI-assisted perception on a connected cane and communicates it through audio.

What we built

  • Mobile app in Expo / React Native
  • NestJS + Prisma backend on Cloud Run
  • Python bridge running on a Raspberry Pi Zero 2W
  • In-house model training pipeline
  • Cane firmware in PlatformIO
  • Nx monorepo with independent deploys per application

One technical decision

The phone connects to the cane over WiFi, but Android decides on its own which interface each socket goes out through: the channel kept dropping even when preflight came back green. We wrote a native Expo module so the operating system opens the socket, and kept our binary protocol in TypeScript. Native transport, typed protocol, one API for both iOS and Android.

Three-dimensional render of the Orisen smart cane: a white cane with blue light guides along its body and a glowing spherical sensor at the tip.
Product render of the Orisen cane.

Wyrdvow

In development · playable end-to-end MVP

Narrative mobile RPG with AI

  • Mobile
  • AI
  • Backend
  • Game design

The problem

An RPG where the character's oath alters rolls, progression and ending. The narrative is generated with AI, but the rules cannot be arbitrary: they have to be reproducible.

What we built

  • Expo 55 app with React Native 0.83 and React 19
  • NestJS 11 API with Prisma 7 and PostgreSQL
  • Deterministic, pure, tested rules engine
  • Runtime contracts shared between app and API
  • Swappable AI adapters and Cloudflare R2 storage
  • Admin dashboard in Vite / React

One technical decision

We separated narrative generation from game rules: the AI writes, the deterministic engine decides. The same run with the same seed always produces the same result, and that is precisely what makes a game with AI inside it testable.

Screenshot of the Wyrdvow app: a narrative scene screen in dark theme, with health and stress bars, the scene text and two decision options flagged as risky.
A Wyrdvow narrative scene in the mobile app.

What we do

One offering and three specialties. If something falls outside this, we say so before the meeting.

Product from zero to production

Technical design, mobile and backend development, infrastructure and deployment. We take on the whole product, not a slice of the ticket.

  • AI applied to product

    Integration with engineering judgement: swappable adapters, versioned prompts, fallbacks and a clear line between what the model generates and what the system decides.

  • Mobile with React Native and Expo

    Two products of our own on Expo, including native modules we wrote ourselves when the JavaScript runtime was not enough.

  • Hardware and software

    Firmware, BLE and WiFi connectivity, and the app that drives it. It is where there is least competition and where we already have something working.

What we do not do

Brochure sites, template-based e-commerce, WordPress, legacy migrations and standalone QA. Not a lack of capability: focus.

How we work

There are two of us. That means you talk directly to whoever writes the code, with no layers in between. It also means rigour is not optional: we have no spare people to fix what went wrong.

  1. Contracts before code

    Runtime schemas are shared between app and API. When a contract changes it breaks at compile time, not in production.

  2. Pure domain logic

    Rules live isolated from infrastructure and are tested without a database or network. The Wyrdvow engine is deterministic by design.

  3. Explicit monorepo boundaries

    Every library declares what it may depend on. Architecture is verified in CI, not in code review.

  4. Decisions in writing

    Decision records, hardening plans and documented scope before touching the code. We write it for ourselves and it ends up serving the client.

  5. Accessibility by default

    We build assistive technology for blind people. This page can be navigated entirely by keyboard and with a screen reader.

  6. No scope surprises

    Scope agreed in writing before we start. If something changes we discuss and quote it; it does not show up at the end on the invoice.

Who we are

Two engineers, no sales team and no management layers. The person who answers your email is the one writing the code.

Let's talk

Tell us what you want to build. You get an answer from one of the two people who would work on it.

It helps us tell you quickly whether we can do it. It is not a fixed quote.

What you want to build, by when, and what exists today.