Guide
Lapentor vs Moorea 2026: the editor or the chain
Two opposite models at a similar budget: an exportable, highly adjustable editor, or the whole chain from raw panorama to a tour delivered under the client's brand, with no quota and no expiry.
Lapentor sells a 360 editor: you compose the tour point by point, you publish it, and for $10 you can take it away onto your own server. Moorea does not sell an editor but the whole chain - the raw panorama goes in, the public link comes out, the tour stays online with no counter and carries your client’s name.
If your subject is a wide site seen from the sky - a golf course, a campsite, a wine estate, a marina - that chain is what decides, not the length of the settings catalogue.
This page is written by Moorea and it is signed: read it knowing that. The Lapentor figures quoted here were recorded on 18 August 2026 from their pricing page and their FAQ; the market benchmarks come from our survey of 17 August 2026. These grids move, so check them before deciding.
Let us start with what Lapentor does well, because it is real and it bounds the rest.
- The ceilings fall early. At $25 a month, unlimited projects and unlimited panoramas per project, where many platforms sell that two tiers higher.
- Customisation is wide. Eight kinds of hotspot, more than twenty plugins, themes for the scene list and the control bar: it is the product’s main argument, and it is owned as such.
- The export genuinely exists. For $10 once, you download an archive containing the code and the images of your tour, and you drop it on your server.
That last point is a real answer to platform dependency, and Moorea has no equivalent. That is the concession, in full. The rest of this page explains why, on a wide site, it is not enough to decide.
The table
| Criterion | Lapentor | Moorea |
|---|---|---|
| Nature of the product | hosted 360 editor, exportable to your server | full chain, from raw panorama to public link |
| Aerial panorama processing | not announced on the public grid | included: multi-resolution tiles, zenith cap filled, logo at the nadir, 6 image adjustments |
| Industry template | none: every tour starts from an empty scene list | golf, campsite, winery, marina, construction, new-build… with the trade's navigation |
| Free tier | 3 projects, 15 panoramas per project | 3 active tours, 5 panoramas each, no expiry |
| Views and bandwidth | no published quota | unlimited, never billed, on all four plans |
| Audience analytics | not detailed on the public grid | included behind no tier, free plan too |
| How long tours are kept | data deleted after three months of an inactive account | no expiry, on any plan |
| Client sign-off inside the tour | no | the Atelier: notes anchored to the view, guests without accounts |
| Delivering under the client's brand | through the export, $10 per project, hosting on you | the client's domain, automatic certificate, badge removed, nothing to administer |
| Public price | free, then $25 a month or $250 a year | €0, €9, €19 or €39 excl. VAT a month |
An editor assumes the panorama arrives clean
In aerial practice, it never arrives clean. So the difference plays out before you open any editor at all.
What Moorea does before the editor
Between the memory card and the link you send the client, Moorea takes charge of the files. Cutting into multi-resolution tiles, generating derivatives, filling the cap above the drone, reprojecting a logo at the nadir under the visitor’s feet.
On top come six image adjustments - exposure, contrast, saturation, temperature, tint, sharpness - whose preview is a real-time shader and whose final render is baked on reprocessing, so it is identical everywhere. Accepted sources go up to 32,000 pixels wide, or about 512 megapixels per viewpoint.
Those are two different layers of the same job, and one does not replace the other: setting a control-bar theme does not fill a zenith cap. A plugin catalogue gives you levers on the finished tour; it gives you nothing on the files going in.
Where our chain stops
The boundary, to be precise: we do not stitch your raw frames. Going from individual shots to an equirectangular panorama stays the job of your stitching software. Our chain starts at the panorama and runs to the public link - the step-by-step detail is on the how it works page.
The industry template, which a plugin catalogue does not compose
A sixty-hectare site is not browsed like a flat. That is not a matter of taste, it is a matter of bearings: with no map, the visitor never knows where they are.
The map places the scenes on its own
Panoramas from a drone carry their coordinates, altitude and heading in the metadata. Moorea reads them and places the scene on a satellite backdrop, which you can then drag by hand.
When the map is not right, the interactive map takes your own image - site plan, campsite map, drawn map - and positions on it are relative, so nothing is lost if you go back to satellite.
The template files the tour the way the trade files it
Above that comes the industry template: golf, campsite, winery, marina, construction progress, new-build development.
Each brings its own way of cutting up and naming the tour - an eighteen-hole course is not filed like a campsite in accommodation zones, a marina is not filed like a building site - and the player’s navigation follows that division instead of lining up thumbnails. On a golf course or a campsite, that structure is the tour.
Interiors go through too
To clear a frequent confusion: interiors work as well. The engine displays any 2:1 equirectangular panorama, wherever it comes from. A panorama of a restaurant room shot from a tripod imports and renders in the same tour as an aerial view. Aerial is our speciality and our difference, it is not a format limit.
No counter, and nothing that expires
No view quota, no bandwidth cap, no expiry - on all four plans, free one included.
That is not a commercial favour: egress from our object storage is free, so billing for audience would be artificial rent. The tour of a campsite that takes its whole year’s traffic in three weeks of June costs us not a euro more than a tour nobody watches.
On traffic, a draw
On this ground, Lapentor is on the right side of the market: their public grid shows neither a view quota nor a bandwidth cap.
Two players in the panel charge for the watching - Klapty bills view overage at €6.99 to €9.99 per thousand, Panoraven sells bandwidth tiers of 20 to 100 GB a month, recorded 17 August 2026. The gap with Lapentor does not open up on traffic, it opens up on duration.
On duration, the gap is clear
A tour nobody touches any more
Lapentor
90 days
a project becomes a candidate for deletion after 90 days without a login, 30 days without a single view and no edits; an account left inactive for more than three months has its data permanently deleted
Moorea
no deadline
no expiry on any plan, free one included: a QR code printed on a welcome sign still works in three years
Their rule targets abandoned accounts, and an active subscription at $250 a year makes it theoretical in most cases.
It still counts in two very concrete situations: a drone pilot keeping former clients’ tours online, and a council whose QR code is engraved on a signpost. The billing model that rations duration is the most widespread on the market; we set out its four variants in the Matterport comparison.
The client’s sign-off happens inside the tour
This is the step nobody equips and that costs the most time: getting the tour approved before publishing. With no tool it happens by email - “the view on hole 7 is too dark”, “there is no pin for the pool” - and half the work is working out which scene is being discussed.
Annotate in the 360, not in an email
The Atelier is a layer you switch on over a tour. The team and guests without accounts annotate directly in the 360: a note is anchored to the scene and to the viewing angle, so opening it puts you exactly where the client was looking.
You talk in a thread, you resolve, you attach an image. The invitation link has its own token, revocable independently of the visibility: a private tour can have an active Atelier.
The principle that matters: a note is not a point of interest. Same anchor, opposite life cycles. The pin is published content; the note is a conversation about the tour. You close the layer to deliver, and the published tour keeps none of it.
Delivering under the client’s brand: two opposite routes
Both products answer the same demand - that the tour carries the client’s name, not the platform’s - by two routes that have nothing in common.
At Lapentor, the export
The answer is the archive: you download the project and you host it. Total control, a very low marginal cost, and an owned trade-off: you handle the server, the certificate and the backups, and you republish on every change. On three tours delivered once, that is excellent. On forty live tours that get retouched mid-season, it is a job.
At Moorea, the client’s domain
The answer is the custom domain. The client creates a CNAME record, the certificate is issued and renewed automatically, the tour is served on their domain, the Moorea badge goes to zero and the accent colour is checked on save at a contrast of at least 3:1 against the player’s dark surfaces.
Public tours are then indexed on the client’s domain, not ours, and a shared link shows their name, their title and their favicon. You administer nothing - and you do not own the files. That is the trade, to be made with your eyes open.
Full white label and the client's domain
The market
€99.90
a month, on Klapty's top tier; elsewhere a one-off add-on of €250 to €699 at 3DVista
Moorea
€39 excl. VAT
a month, on our top tier: client domain, certificate issued and renewed automatically, badge removed, unlimited tours
What the chain costs
Our public grid runs from €0 to €39 excl. VAT a month, and what you pay for is a tier of capabilities, never a counter: the top tier is unlimited in number of tours. What the subscription covers is set out on the hosting page.
For embedding in a page, the iframe weighs about 142 kilobytes gzipped on the critical path, measured on every build, and sets neither cookie nor session. The rendering engine itself is 19.5 KiB gzipped, with no external dependency. The API and the database are in Frankfurt, an infrastructure fact that is useful if your legal department asks.
When Lapentor is enough
Three specific situations where we point you their way without hesitating.
You have to hand over the files, not an access. A museum archiving its tours, a public body whose specification requires internal hosting, an agency that delivers an archive and closes the file: the $10 export answers exactly that, and no subscription replaces it. Moorea offers no export of that kind today.
Your subject is a standard interior and you already run a server. Tripod panoramas, room by room, with no map to carry and no aerial processing to do. Moorea displays those tours perfectly well, but a good part of its chain never shows itself, and if hosting a static folder does not scare you, your cost of ownership will be unbeatable with them.
You want a very particular interface behaviour. A tour that needs a specific plugin, an unusual mechanic, a particular control-bar theme: their catalogue goes further than our settings, which are deliberately bounded so that tours age well.
Outside those three cases, the question is no longer the editor.
What you can look at now
If you produce tours of wide sites, want to keep them online with no counter and no expiry date, organise them with a template made for your trade and deliver them under your client’s name, the product page shows the player at work and the pricing grid fits in three lines.
The golf landing page gives a full example of what the template changes about a tour, and the aerial virtual tour page explains why the sky changes the way a place gets told.
Développeur et télépilote de drone. Construit Moorea au sein d’Elvn Studio.
A place worth showing from above?
The free plan is enough to publish a first tour and show it around.