If you need someone to build your drone software, this list compares five companies that do it, and it uses one test to sort them: whether they will tell you the name of a single drone client. Four of the five build custom software for other companies. All five are real, and each one fits a different kind of buyer.
CodigoDelSur publishes this list and appears on it. That is a conflict of interest, so the list is built so you do not have to take our word for anything: every claim about every company below comes from that company's own website, checked in September 2026, and every claim about our own work links to a case study or to an app you can open right now.
How this list was built
There is no directory for drone software development. Clutch, GoodFirms and DesignRush all have categories for iOS, Android and Flutter, and none of them has one for drones. That means there is no ranking to appeal to and no rating to quote, so this list uses criteria you can check yourself instead.
Three of them:
First, named drone clients. Anyone can write "we build drone software" on a services page. Very few companies will tell you whose drone software they built, because that requires a client who agreed to be named. It is the single hardest thing to fake and the fastest thing to verify.
Second, what they actually shipped. Flight control, mission planning, image processing and fleet dashboards are different disciplines. A company that processed drone imagery has not necessarily written a line of flight code.
Third, where the delivery team sits and whether the company says so. Drone projects involve hardware in a field somewhere, and hardware problems happen during the workday, not after it. A team that is asleep when your pilot is flying costs you a day per question.
What is deliberately not in this list: employee headcount as a proxy for quality, ratings from directories, and awards. None of the three tells you whether a team has flown a drone from code they wrote.
The five, compared
Same six fields for each company, in the same order.
CodigoDelSur. Where the team sits: Montevideo, Uruguay, working the client's business day. Named drone clients: four, each with a published case study. What it builds in drones: flight apps, automated mission capture, mapping and reality capture platforms, warehouse inventory dashboards. DJI SDK: yes, in three of the four named projects. Engagement models: staff augmentation, dedicated teams, full product ownership. Best for: a product team that needs to be available during your working day and wants to see the work before signing.
Chetu. Where the team sits: headquarters in Sunrise, Florida, with delivery centers in Noida, India. Named drone clients: none. What it builds in drones: the broadest published scope of the five, covering fleet management, video transmission to ground stations, swarm coordination APIs, autonomous flight, payload integration for RGB, infrared, LiDAR and radar, geofencing, delivery and precision agriculture. DJI SDK: not mentioned. Engagement models: on-demand developers and dedicated teams. Best for: a buyer who wants one vendor with a very large bench and does not need to see who else they have done this for.
Intellias. Where the team sits: Ukraine, Poland, Portugal and other European locations, with more than three thousand people. Named drone clients: none. Its published drone case studies describe clients as "a leading US provider of drone data and navigation software" and "a leading agriculture software company". What it builds in drones: the deepest published work of the four others, including a cloud navigation system with aeronautical mapping, airspace management, geofencing, traffic management, remote ID, pre-flight planning and flight operation apps, plus agricultural field mapping and 3D modeling. DJI SDK: not mentioned; they describe SDKs of their own. Engagement models: dedicated teams and large programs. Best for: an enterprise program that needs hundreds of engineers and does not need named references.
Vention. Where the team sits: headquarters in New York, with delivery centers whose locations are not published. Named drone clients: one, Vexcel Imaging. What it builds in drones: batch processing and machine learning analysis of aerial imagery, in-browser mapping applications. DJI SDK: yes, and it is the only company on this list other than us that mentions it. Engagement models: staff augmentation, dedicated teams, project outsourcing. Best for: a buyer whose problem is imagery at scale rather than flight.
Softeq. Where the team sits: headquarters in Houston, Texas, with teams in Munich, Los Angeles, Vilnius and Guadalajara. Named drone clients: one, Sky-Futures. What it builds in drones: a client portal and backend for industrial inspection, with image and video processing from inspection drones, fault detection on 2D imagery, document management and generated reports. DJI SDK: not mentioned. Engagement models: dedicated teams and staff augmentation. Best for: an industrial inspection product where the hard part is the data, not the aircraft.
What the comparison actually shows
Add up the named drone clients across the four companies other than us and you get two: Vexcel Imaging at Vention, and Sky-Futures at Softeq. The two largest companies on the list, with more than five thousand people between them, name none.
This is not a gotcha. There are good reasons a development company cannot name clients, and the most common one is that the contract forbids it. But it changes what you can do as a buyer. When nobody will name a client, the only things left to compare are headcount and the services page, and both of those are written by the seller. A named client is the one claim you can go and check without asking anyone's permission.
The same thing happens with the DJI SDK. Most drone products in the world are built on DJI hardware, so integrating with the DJI SDK is close to a requirement. Of the five companies here, two mention it.
1. CodigoDelSur
CodigoDelSur has been building software since 2007 from Montevideo, Uruguay, for clients in the United States and the rest of the world. Roughly a hundred and forty people, more than two hundred and fifty clients, and products that have reached more than three hundred million users.
The drone work spans four named clients and a decade.
DroneDeploy is a drone mapping and reality capture platform. CodigoDelSur worked on automated flights, pre-flight and in-flight safety checks, map data exploration, and detailed flight logs used for compliance, insurance and fleet maintenance, across iOS, Android and web, with the DJI SDK. DroneDeploy was acquired by Procore in July 2026.
Skippy Scout is a drone-enabled crop scouting app that automates flights to capture images at scouting points across a field, so an agronomist gets a consistent set of images instead of whatever the pilot remembered to photograph. iOS, built on the DJI SDK.
AgroScout is a precision agriculture platform used by growers, agronomists, food processors and insurers to monitor crop health from drone, satellite and phone imagery. CodigoDelSur built the mobile application for iOS and Android on the DJI SDK and Mapbox: flight control, altitude management and camera triggering. Image processing stayed with AgroScout's own pipeline, and the pest and disease detection models are the client's own work, not ours.
Ware built warehouse inventory management using drones flying indoors. CodigoDelSur built the frontend of the platform. Ware was acquired by Gather AI.
Across those four, the recurring pattern is the unglamorous part of drone software: getting a flight to happen the same way twice, getting the images off the aircraft, and getting them in front of someone who has to make a decision about a field or a warehouse aisle. Three of the four run on the DJI SDK.
Engagement models are staff augmentation, dedicated teams, and full product ownership from zero to launch. The minimum commitment is two weeks, or one sprint. On a dedicated team the most senior developer makes the technical calls, and the assigned project manager is included rather than billed separately. If someone has to be replaced, the replacement overlaps with the outgoing developer for ten business days and that overlap is not billed. The working day is Uruguay time, which overlaps with both United States coasts.
Where CodigoDelSur is the wrong choice: if you need hundreds of engineers on a program at once, or you need a team physically on your site, this is not the fit. Intellias is built for the first and Chetu for the second.
2. Chetu
Chetu is a large custom development company headquartered in Sunrise, Florida, founded in 2000, with more than twenty-eight hundred developers and delivery centers in Noida, India.
Its drone page is the most comprehensive of the five by a wide margin. It covers fleet management, live video transmission to ground stations, swarm coordination APIs, autonomous flight, payload integration for RGB, infrared, LiDAR and radar sensors, geofencing, last-mile delivery and precision agriculture. If you can describe a drone software problem, that page claims it.
What the page does not contain is a single named drone client, a case study, or a mention of the DJI SDK. For a buyer, that means the evaluation has to happen entirely in the sales conversation, because there is nothing published to check beforehand.
Chetu is the right call if you want a single vendor with a very large bench who can staff quickly across several unrelated systems at once, and if you are comfortable evaluating that in meetings rather than in public evidence.
3. Intellias
Intellias is a European engineering company with more than three thousand people across Ukraine, Poland, Portugal and other locations. Of the four companies here other than us, it has the deepest published drone engineering.
Its published work includes a cloud navigation platform for drones with aeronautical mapping, airspace management, geofencing, traffic management and remote ID, along with pre-flight planning and in-flight operation applications and its own map SDKs for web, iOS and Android. On the agriculture side it covers field mapping, UAV data processing, 3D modeling, aerial scouting, plant counting and spraying. This is genuine, specific work, described in detail.
It is also entirely anonymous. The clients in those case studies are "a leading US provider of drone data and navigation software", "a leading provider of aeronautical data and software for drones navigation" and "a US technology startup". Quotes are attributed to a job title, never to a company.
The other consideration is time. Intellias delivers from Eastern and Central Europe, which is six to nine hours ahead of the United States. For a program with a fixed scope and a long runway that is fine. For a product where a field test on Tuesday morning generates three questions, it means those questions get answered on Wednesday.
Intellias is the right call for an enterprise program that needs scale and a formal delivery structure, and where named references are not part of how you buy.
4. Vention
Vention is a development company founded in 2002, headquartered in New York, with more than three thousand people and delivery centers whose locations it does not publish.
Its drone work is centered on imagery rather than flight. For Vexcel Imaging, which it names, it built batch processing and machine learning analysis of aerial imagery along with in-browser mapping applications. It is also the only company on this list other than CodigoDelSur that mentions the DJI SDK, alongside ROS and the Dronecode SDK.
Vention is the right call if your problem is what happens to the imagery after the flight, at volume, and if you are comfortable not knowing which country the engineers will be in.
5. Softeq
Softeq was founded in 1997 and is headquartered in Houston, Texas, with more than two hundred engineers and teams in Munich, Los Angeles, Vilnius and Guadalajara. It is the smallest company on this list and the only one besides CodigoDelSur with a named drone client and a home office in the United States.
That client is Sky-Futures, in industrial drone inspection. Softeq built the client portal and backend, with processing of images and video captured by inspection drones, fault detection on 2D imagery, document management and generated reports.
The work is real and it is documented, but it is a single project presented as a featured case rather than a drone practice: there is no drone services page, and no mention of flight control, mission planning or the DJI SDK.
Softeq is the right call for an industrial inspection product where the value is in the analysis pipeline, and where having engineers in Houston and Guadalajara matters to you.
Which of the five fits your situation
You need an app that flies a DJI aircraft on a repeatable route and gets the images back: CodigoDelSur or Vention. They are the two that mention the SDK that job requires.
You need a program with hundreds of engineers and a formal structure, and you buy on capability rather than references: Intellias.
You need one vendor to cover several unrelated systems at once with a large bench: Chetu.
Your problem is the analysis pipeline after the flight, for industrial inspection: Softeq, or Vention if the volume is very large.
You want to see who else the team has done this for before you sign, and you want them reachable during your own working day: CodigoDelSur. That is the situation this list is written for, and it is fair to weigh that accordingly.
What a drone software project usually involves
Three things surprise buyers who are commissioning drone software for the first time.
The first is that the aircraft is the easy part. The DJI SDK gives you flight control. What it does not give you is a repeatable capture: the same altitude, the same overlap, the same points, in wind, by a different operator, next month. That reliability is most of the work, and it is why Skippy Scout and DroneDeploy both spend so much of their code on the routine before takeoff rather than on the flight.
The second is that the data volume becomes the product. A single flight over a field produces hundreds of images. Deciding what happens to them, where they are stored, how they are stitched, and what a person sees when they open the app, is a bigger engineering problem than the flight was.
The third is that regulation is a feature, not paperwork. Flight logs, geofencing and remote ID are not compliance overhead added at the end. They are product requirements that shape the data model, and retrofitting them is expensive.
Frequently asked questions
How do I check that a drone development company has actually shipped drone software?
Ask for the name of one drone client and the app in the store. If the answer is a description rather than a name, that is not evidence of anything. It may still be a good company with a strict contract, but you are now buying on trust rather than on proof, and you should price that accordingly.
Do I need a company that has used the DJI SDK before?
If your hardware is DJI, yes, and it will save you weeks. The SDK has behaviors that are not in the documentation and are learned by flying. If your hardware is a custom airframe or Parrot, ask instead about the specific SDK you will use, and treat DJI experience as evidence of the general skill rather than as the skill itself.
Does the team's timezone actually matter for drone work?
More than for most software, because drone development involves someone standing in a field with hardware. When a test flight raises a question, a team that shares your working day answers it that afternoon. A team six to nine hours ahead answers it the next day, and a two-week test cycle becomes four.
What about the big consultancies?
Accenture, EPAM and Globant can all staff a drone project. They are built for programs measured in years and in hundreds of people, with the pricing and process that implies. If your drone product is a team of four to fifteen people, you will be a small account there, and small accounts get the attention that small accounts get.
How fast can a team start?
At CodigoDelSur, days rather than weeks, with a minimum commitment of two weeks or one sprint. The larger companies on this list generally quote a longer ramp, because a bigger bench means a longer internal matching process.
Who owns the code, and what happens when the engagement ends?
At CodigoDelSur the client owns the code, the repositories and the store accounts throughout, and an engagement ends with a handover to whoever takes it over. Ask every company on this list the same question in writing before signing, including what happens to the store accounts, because that is the one that gets forgotten.
Can you work on an existing drone product instead of starting from scratch?
Yes, and it is common. Of the four drone projects listed above, some were built from zero and some were joined in progress. Taking over an existing codebase is a distinct skill from starting one, so ask specifically about it if that is your situation.
What is the difference between a drone software company and a drone software development partner?
A drone software company sells you a product it already built, and you adapt to it. A development partner builds the product you specify, and you own it. If an off-the-shelf platform already does what you need, buying it is almost always cheaper and faster. Commissioning custom software makes sense when the thing you are building is the business rather than a tool for it.
How this list was built, in one paragraph
Every company on this list was checked on its own website in September 2026. Claims about scope, team locations and client names come from what each company publishes about itself. Named client counts were established by reading each company's drone case studies and services pages and counting the clients identified by name. No ratings, directories or third-party rankings were used, because none of them has a drone category. CodigoDelSur publishes this list and is on it, which is why every claim about our own work points to a case study or an app you can open.
