Skip to main content
Ushba Tech

Mestia, Georgia

We build web platforms, APIs and AI systems.

For the last two years we have been building them for travel: flight search, hotel inventory, booking flows and activities. It is unforgiving, high-volume, integration-heavy work — and it is the work we know best.

Talk to an engineerSee what we build

You will get a reply from someone who writes code, not a sales sequence.

Suppliers

  • Flight GDS and carriers
  • Hotel banks and channels
  • Activity providers

Ushba Tech

  • One data model
  • Reconcile
  • Cache
  • One API

Your product

Web · Mobile · Partner APIs

Every supplier has its own data model. We absorb that so your product does not have to.

Track record

Trusted by

Flight search and booking platform. We build and maintain the infrastructure behind it.

Building software and infrastructure
Since 2024Building software and infrastructure
Registered company · ID 435898110
GeorgiaRegistered company · ID 435898110
Serving live travel booking traffic
In productionServing live travel booking traffic

What we do

An engineering team you can hand a hard system to

We are generalists by training and specialists by experience. The four things below are what we are asked for most.

  • Web platforms

    Product engineering end to end — architecture, backend, frontend, deployment. We take ownership of the whole system, not a ticket queue.

    • Next.js / React
    • PostgreSQL
    • Multi-tenant systems
  • APIs and integrations

    Versioned REST APIs designed to be consumed by other people, and the unglamorous work of integrating suppliers whose contracts disagree with each other.

    • API design
    • Third-party integration
    • Webhooks and queues
  • AI systems

    LLM features built to a spec and evaluated against it: search and ranking, extraction, assistants. Shipped with fallbacks, because models fail in production.

    • Retrieval and search
    • Structured extraction
    • Evaluation
  • Performance and reliability

    Making systems fast and keeping them up: caching layers, load shedding, observability. Latency budgets treated as a product requirement.

    • Caching strategy
    • Observability
    • Load and stress testing

Where we go deep

Travel infrastructure

Travel technology punishes shortcuts. Inventory is stale the moment you cache it, suppliers each have their own idea of a data model, and a booking that half-succeeds is worse than one that fails. We have spent two years in that problem space.

  • Flight infrastructure

    Search across suppliers, normalise fares and ancillaries, hold and issue. The hard part is never the request — it is reconciling suppliers that disagree about availability, and staying fast while doing it.

    • Search and pricing
    • Booking and ticketing
    • Fare rules

  • Hotel APIs

    Static content and live availability from multiple sources, mapped onto one property model, cached hard enough to be usable and invalidated carefully enough to be honest.

    • Inventory mapping
    • Rate plans
    • Content pipelines

  • Activities and experiences

    Tours, tickets and experiences: timeslot inventory, capacity, cut-off rules and cancellation windows — the parts that quietly break when a supplier changes a field.

    • Timeslot inventory
    • Capacity rules
    • Vouchers

  • Booking flows

    The journey from search to confirmation, where most revenue is lost. Session integrity, price-change handling, payment, and failure states that tell the truth.

    • Checkout
    • Payments
    • Post-booking

How we work

No discovery theatre

Four steps, and none of them is a slide deck. If a step is not earning its place on your project, we skip it and say so.

  1. We read your system first

    Before proposing anything we look at what exists — the code, the suppliers, the constraints you cannot change. Most bad estimates come from skipping this.

  2. Scope, in writing

    A written scope with what is in, what is out, and what we are unsure about. The unsure list matters more than the rest; it is where the surprises live.

  3. Ship in slices

    Working software in production early, then extended. You see progress you can click on, not a status report about progress.

  4. Hand over properly

    Documentation, runbooks and a team that can operate it without us. We would rather be re-hired than depended on.

About

Named after the mountain above our door

Ushba is the twin-peaked summit standing over Mestia, in the Svaneti mountains of Georgia. It has a reputation among climbers: technical, unforgiving, and worth it. We took the name because that is the kind of work we like.

We have been building software and infrastructure together since 2024. Ushba Tech LLC is the newer part of the story — we incorporated in Georgia in June 2026, to put a company around work that was already running in production.

We are a small team and intend to stay one. That is a deliberate constraint: it means the people who scope your project are the people who build it.

Company details

Legal name
Ushba Tech LLC
Legal form
Limited Liability Company
Registration ID
435898110
Registered office
E. Parjiani St. N 6, Mestia, Georgia

Registered with the LEPL National Agency of Public Registry, Ministry of Justice of Georgia. Our entry can be verified independently at napr.gov.ge.

Contact

Tell us what you are building

Send us the shape of the problem and we will tell you honestly whether we are the right team for it — including when we are not.

Rough is fine. The system you have, the problem you are hitting, and any deadline you are working to.