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.

What SpearAtlas is

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.

The problem we are solving

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.

What shipped at launch

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. Later journal entries cover Version 2 work that followed this launch—orthomosaic layers, the Gaussian splat room, dense point clouds in Space, and more.

Maps, basemaps, and CRS

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.

How to get started

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.