Platform · April 21, 2026
SpearAtlas is live: one hub for organized drone and reality-capture delivery
We are introducing SpearAtlas as the workspace where mission outputs become clear, client-ready delivery—without scattered links and fragmented handoffs.
Today we are opening SpearAtlas as the place teams use to organize, present, and hand off drone and reality-capture work. The platform is built around a simple idea: your mission deserves a single, intentional delivery surface—not a pile of files, ad hoc folders, and one-off share links.
SpearAtlas is a mission hub for aerial and geospatial projects. Each project becomes a structured workspace where orthomosaics, 3D meshes, video, PDF reports, CAD references, supporting files, hosted URLs, and inspection imagery live in clear rooms—so stakeholders see the story of the job, not a scavenger hunt.
The experience is tuned for delivery: readable hierarchy, consistent presentation, and shareable access when you are ready to bring clients or partners in. Underneath, the same patterns apply whether you are on a lightweight media tier or running full mapping and collaboration workflows.
Drone and photogrammetry workflows produce excellent data—and too often lose clarity at the handoff. Deliverables end up split across drives, inboxes, and generic file tools. Clients get links without context; internal teams lose track of which ortho, model, or report is authoritative.
SpearAtlas reduces that fragmentation. Project rooms keep outputs grouped by role—maps, models, media, documents, embeds, and supporting material—so the path from upload to review to client delivery stays obvious for everyone involved.
At launch, SpearAtlas centers on the Mission Hub: per-project spaces for the outputs you already capture and process. You can bring orthomosaic hosting, 3D viewing, video and imagery, PDF reporting, CAD plan references, URL embeds for external tools, and supporting files into one coherent layout.
- Structured mission outputs aligned to how teams actually deliver work
- Clear separation between map, model, media, document, and embed surfaces
- Workflow-oriented organization instead of flat file dumps
- Client-facing presentation that stays consistent across projects
- Tiered access so teams can start small and scale into deeper mapping and collaboration as needs grow
Exact capabilities depend on your plan; see Pricing for the current matrix. The launch scope above reflects what is available today. Where this update discusses upcoming direction, we state it explicitly as planning work—not as something already fully live in the product.
From intake through delivery, SpearAtlas favors clarity. Uploads land in a project context. The Mission Hub surfaces the orthomosaic, mesh, report, and collateral in predictable places. When it is time to share, you are pointing people at a single project experience rather than reconstructing the narrative in email.
For operators juggling multiple sites or repeat clients, that repeatability matters: the same structure every time, less re-explaining, fewer mistakes about which file is current. For recipients, it reads as intentional—which is the bar for premium field services.
SpearAtlas is for survey and mapping shops, drone service providers, internal geospatial teams, and anyone who needs to turn captures into confident, presentable delivery. If your work produces maps, models, reports, or rich media and you care how that work is received, this hub is for you.
Everything in this section is planned work—not something you should expect to be complete in the product the day you read this. We are not announcing timelines; details will evolve as we ship and learn.
We plan to support .ply-based workflows, including Gaussian splatting–related pipelines where .ply is the practical interchange. We also intend broader point cloud file support than SpearAtlas offers today.
In the orthomosaic room, we plan a future layer system on top of today’s georeferenced TIFF hosting—so review can extend to multiple TIFF-based layers when the job requires comparison or stacked context, without abandoning a single clear primary ortho.
Workflows we are designing toward include date-to-date TIFF comparisons for progress, RGB-to-thermal comparison when both are delivered as separate georeferenced layers, and other multi-layer map review patterns that depend on the project.
If an orthomosaic does not show satellite imagery underneath it, two practical explanations are common. First, the TIFF may be missing or incomplete georeferencing metadata SpearAtlas needs to place the raster correctly and pair it with a basemap. Second, SpearAtlas may not yet support the coordinate reference system or region you are working in.
If you believe your region or CRS should be supported, or you are unsure which case applies, contact support and tell us the region you are working in. That context helps us prioritize coverage and, when needed, point you to the right fix.
We read what you send. If something feels unclear in the product, breaks your workflow, or should work better for your region and data, reach out—specific examples and project context make the biggest difference. Do not hesitate to contact support; it directly informs what we build next.
This news hub will carry product updates, release notes when we ship meaningful changes, and occasional framing pieces like this one. No noise—just what helps you use SpearAtlas well.
Create an account and open a project. Add your first mission outputs, walk the Mission Hub as a client would, and adjust titles or room emphasis until the delivery story matches how you work. If you are choosing a tier, start from the workload you deliver most often and scale up when collaboration or advanced mapping surfaces become necessary.
We are glad to have you on the platform—and we will keep shipping with the same restraint and product focus reflected here.