Skip to content
About

We started because the software was bad.

Cloud Vector was founded in 2024 to build operations software that holds up outside a demo — in the hands of people doing the actual work, in the conditions it actually happens in.

2024 Year founded
2 Products in production
1 Industry served
0 Templates used
02Why we exist

Aviation software has a pattern.

It demos well and fails on the ramp. It assumes connectivity that isn't there. It asks for eleven taps when a technician has one free hand. It produces records that fall apart the moment someone disputes them.

We built TowTracker first, because line service technicians needed every aircraft movement attributable — who moved what, when, and what condition it was in. Not for a dashboard. For the conversation that happens when something gets damaged and nobody agrees on the sequence of events.

RampRat came from watching crews hunt through binders and stale PDFs for a servicing spec they needed immediately. We put the library on the device, made it searchable by model, manufacturer and ICAO type code, and made it work with no signal at all. Ramp connectivity is unreliable by nature — hangars, aprons and remote stands are precisely where coverage fails.

We are a small team, deliberately. The people who design your software are the people who build it, and you can reach them. That is not a scaling strategy; it is the reason the work is good.

Founded
2024
Team
Small, in-house
Industry
Aviation ground ops
Focus
Mobile + cloud
Location
United States
Response
One business day
03How we work

Four things you can hold us to.

Stated plainly enough that you could check whether we did them.

01 We run what we build Operators, not vendors

TowTracker is our product, in production, with our name on the support address. We carry the consequences of our own architecture decisions, which is a materially different incentive from shipping and moving on.

02 Designed against the real environment Gloves, daylight, one hand

Interaction cost is the constraint that matters in field software. We prototype against the conditions the work actually happens in — cold hands, bright sun, no free hand, no patience.

03 Auditable by default Attribution from the first schema

Who did what, when, is designed into the data model rather than added before a compliance review. It is the difference between a record that settles a dispute and one that starts an argument.

04 You own the result Code, infrastructure, accounts

Repositories, cloud accounts and deployment pipelines are yours from day one and stay yours. There is no layer of ours you have to keep paying for to keep your software running.

04 Contact

Work with a team that answers its own email.

Small enough that you talk to the people building your software. Established enough to have products running in production.