A meadow with a winding path, a mown field and tree cover, reconstructed in 3D from 77 drone photographs
Mown field · area1,505.4 m²
Meadow crossing94.6 m
Canopy above field+11.6 m
Drone photogrammetry, measured

Maps you can measure. Numbers you can defend.

Upload a drone flight. Get an orthomosaic, surface and terrain models, a point cloud and a mesh, with tools that show how far each figure could be off, and refuse when the data cannot support one.

Start free, two flights Open the demo workspace

No card. No sales call. Your first two flights are free.

Aukerman · public-domain survey 77 photos · Sony DSC-WX220 5.0 cm / px EPSG:32617 · E 436846.77 N 4572947.14 Live 3D of a real reconstruction. Drag to turn it.
Measured, not projected

Every number on this page came from a real run.

We have no customer logos to show you yet, so we are showing the work. These figures are from two public survey flights processed end to end on the production system.

29.1min
From 77 photos to all five deliverables, unattended, on a GPU worker.
77of 77
Cameras aligned on that flight. The count is reported on every job.
8ms
To read and encode a native-resolution map tile from a 93 MB orthomosaic.
61.3M cells
Of elevation checked against an independent reader. Exact agreement.
How it works

Four steps, and nobody has to stay awake.

01 / UPLOAD

A bad upload is caught in seconds, not after an hour of processing.

Drop loose photos or an archive. It is opened in your browser and every file is checked before a byte is sent.

  • Zip, tar, RAR and 7z are unpacked on your machine.
  • Each file is identified by its first bytes, not its name.
  • An incomplete upload is refused. A map from 60% of a flight has a hole in it that passes every later check.
Illustration. The photo count and size are the first production flight's.
02 / RECONSTRUCT

The site is rebuilt in 3D while you do something else.

Photos go straight from your browser to storage. A worker starts, reconstructs the site, writes the deliverables back and shuts down.

  • 29.1 minutes for 77 photos on a GPU worker. 44.2 on CPU.
  • The dense stage alone went from 24.4 minutes to 4.2.
  • A faster setting exists. It shifted the map about 15 cm, so it is not used.
Aukerman · Flight-001 · 3D
The demo workspace in 3D view: the meadow's surface model with the orthomosaic draped over it and a measured boundary drawn on the mown field
The demo workspace, 3D view. Surface model with its orthomosaic draped over it.
03 / MEASURE

Draw once. Read length, area, height and volume.

Click to place points, double-click to finish. If you have used a survey tool before, your hands already know this one.

  • Distance with 2D and 3D length, slope and an elevation profile.
  • Area with perimeter and the height range across it.
  • Volume as cut, fill and net, against the base surface you choose.
Meadow crossing · elevation profile
A distance measurement across the meadow reading 94.59 metres, with its elevation profile drawn beneath the map
A 94.6 m line across the meadow, with the ground profile beneath it.
04 / KNOW HOW SURE

Beside every volume: how far off it could be, and why.

A volume arrives with a bound, the reasons behind it, and a plain statement of what the bound does not cover.

  • When a figure is smaller than its own uncertainty, the panel says so.
  • Without ground control, heights are good for differences, not as heights above sea level.
  • Where the boundary runs off the map, no figure is produced.
Mown field · volume
A volume measurement of net 21.5 cubic metres, with a panel beneath it stating it could be off by 75 to 226 cubic metres and that the figure is smaller than its own uncertainty
The demo workspace, measured by the production engine: net 21.5 m³, which could be off by 75 to 226. The panel says the figure is smaller than its own uncertainty.
OJAS Gauge · the measurement engine

A wrong number that looks right is worse than no number.

Earlier versions of this engine shipped three of them. One volume was 5.6 times too high. Each looked reasonable. Gauge is what we built afterwards.

What it does

Reads the surface and terrain models and answers with a figure, its bound, and the reasons for the bound.

Fill and cut over a boundary. Height along a line. Contours, slope, and the footprint of anything standing two metres above the ground.

What it won’t

Return a plausible figure when the data cannot support one.

Where cells are missing it reports “not produced” instead of filling the gap. Where the model has no ground control it says so beside the figure.

not produced

Cells are missing

The boundary crosses ground the flight never covered. No base surface can be built, so no volume is given.

heights are relative

No ground control

Differences within the flight hold. Position on Earth is good to 2–6 m, and the panel says that beside every height.

smaller than its uncertainty

The figure is too small to trust

When the bound is larger than the result, you are told the boundary may enclose no net volume at all.

What it cannot do yet. Photogrammetry cannot reconstruct water, glass or moving vegetation, and the engine cannot tell when a boundary is over one. On our own test site a flat pond came back with heights spread across several metres, every cell marked valid. The bound does not hold there. Until a per-cell confidence measure ships, keep boundaries off surfaces like these.

What you get back

Five deliverables, in the formats your tools already open.

Sizes and counts below are from the first production flight: 167 photos of a 500 m site at 5 cm per pixel.

Orthomosaic

One flat, to-scale photograph of the whole site.

Format
GeoTIFF (COG)
Size
164 MB

Surface model

The height of everything visible: buildings, trees, stockpiles.

Format
GeoTIFF
Cells
61,271,466

Terrain model

The bare ground, with everything standing on it removed.

Format
GeoTIFF
Size
93 MB

Point cloud

Every reconstructed point, in colour, for your own tools.

Format
LAZ
Points
20,834,638

Mesh

A surface of triangles. Geometry today; textures are not delivered yet.

Format
OBJ
Triangles
325,523
Accuracy, stated plainly

How good the numbers are depends on what you put on the ground.

Sizes inside a map are reliable. Where that map sits on Earth is not, unless you placed surveyed markers before the flight.

1–3 × pixel size

Within one map

Lengths, areas and height differences. At 5 cm per pixel, that is 5 to 15 cm.

2–6 m

Position on Earth, no markers

Set by the drone’s own GPS. Fine for “how big is this”, not for setting out.

GCP supported

With ground control

Add a control file at upload and the map is fixed to your surveyed markers on every plan.

The OJAS family

What exists, what is being built, and what is only a name.

We would rather you knew which is which before you sign up than find out after.

OJAS 4D

The platform. Upload a flight, get a map you can measure, keep every flight of a site in one place.

Available

OJAS Gauge

The measurement engine. Volumes, contours, slope and structures, or the reason it cannot give them.

Available

OJAS Delta

Change between flights. Fly the same site again and get the difference computed. It has not yet been run on two real flights of one site.

In development

Ask OJAS

Put a question to your sites in words and get an answer built from the same measurements, with the same refusals. On Pro and above.

Available

OJAS Fields

Crop and vegetation maps from the same flight.

Planned

OJAS Swift

A map in minutes at the edge, where there is no network to send the photos to.

Planned

OJAS Lens

Capture with a phone what a drone cannot reach.

Planned
Pricing

Priced by the month, not by the map.

Paid plans process as many flights as you fly, within a fair-use ceiling. There are no overage charges on any plan.

Trial

$0

Two flights, free. See a real deliverable before paying anything.

  • 2 flights, up to 200 photos each
  • All five deliverables
  • Full measurement engine
  • Ground control supported
Start free

Solo

$39/ month

Unlimited flights for the operator who flies their own sites.

  • Unlimited flights
  • Up to 800 photos per flight
  • One flight processing at a time
  • Ground control and volumes
Choose Solo
For teams

Pro

$99/ month

For teams billing off the numbers, and comparing sites over time.

  • Unlimited flights
  • Up to 2,000 photos per flight
  • Three flights at once
  • Change between flights in development
  • Ask OJAS, the in-app assistant
Choose Pro

Scale

$299/ month

Survey firms and multi-site operators running a queue all week.

  • Unlimited flights
  • Up to 2,500 photos per flight
  • Eight flights at once
  • Priority queue
  • Ask OJAS and API tokens
  • Named support contact
Choose Scale

Prices in US dollars, billed monthly, tax added at checkout where it applies. “Unlimited” is subject to fair use: 60 flights a month on Solo, 200 on Pro, 600 on Scale. Change between flights is marked in development: it has not been proven on real data, you will not be charged more when it ships, and you should not choose Pro for it today.

Questions

Asked before signing up.

Something else? Write to info@celesticlabs.org. A person reads it.

Which drones and cameras work?

Any camera that writes ordinary JPEG photos with GPS position in them. The two flights on this page were taken with a Sony DSC-WX220 and a near-infrared survey camera. Photos without GPS can still be placed from their overlap, with less certainty about where the map sits.

How should I fly to get a good map?

A back-and-forth pattern with the camera pointing down, and each photo overlapping its neighbours by 70 to 80 percent. Even light helps. Water, glass, snow and crops moving in wind reconstruct badly with any photogrammetry tool, this one included.

How accurate are the measurements?

Within a single map, about one to three times the pixel size, so 5 to 15 cm at 5 cm per pixel. The map’s position on Earth is good to 2 to 6 m unless you add ground control points. Every volume also carries its own bound and the reasons for it.

What happens to my photos?

They go from your browser directly to storage, are used to build your deliverables, and stay in your account. They are yours. The privacy page says what is kept and for how long.

Can I use the results in my own software?

Yes. Every deliverable downloads in a standard format: GeoTIFF for the orthomosaic and elevation models, LAZ for the point cloud, OBJ for the mesh. They open in QGIS, ArcGIS, CloudCompare, Civil 3D and the like.

Who is behind this?

OJAS 4D is made by CelesticLabs, a company in Hubballi, India, that works on how autonomous machines keep a trustworthy account of their surroundings. The same rule runs through both: say how sure you are, and refuse when you are not.

Do you have customers I can talk to?

Not yet. The product is live and nobody has paid for it. That is why this page shows measured runs instead of logos, and why the first two flights are free.

Start

Fly it. Upload it. Measure it.

Two flights free, with every deliverable and the full measurement engine.

Start free Open the demo