Launch Pad is Verge Ag's path planning and route optimization platform. There are four ways to put it inside your product, from no code at all to a fully custom build. Every one of them gives your users professional path planning and gives you a single bill. What changes is how much of the experience you build yourself.
In every option Launch Pad does the path planning. What differs is who builds the screens around it and how the finished plan gets back into your product. Most partners start with One-Click Launch and move up only when their product needs more control.
No code
Your logo, your subdomain and your billing on Launch Pad as it is. Your customers plan in Launch Pad directly.
A few API calls
Send a boundary, get a path plan back. Launch Pad's route editor opens from your product, already signed in on the right field.
Full API build
Your UI, our planning engine. You send boundaries and settings, get plans back as data, and render and dispatch them yourself.
Custom project
Launch Pad inside your FMIS as if it were built there: your design system, your workflows, your sign-in. Scoped and built together.
Launch Pad as it is today, under your brand. Your customers sign in to Launch Pad with your logo on screen, at your own subdomain if you want one. You onboard and manage them from a single partner admin account and receive one consolidated bill. There is nothing to build.
Talk to Us About White LabelNothing. Send us a logo and pick a subdomain; we set up your partner admin account and you start onboarding customers.
Accounts, the planning interface, hosting and every product update. Billing is consolidated under you: your customers never see credits or invoices.
Dealers, agronomy service providers and resellers who want to offer path planning under their own brand without engineering work.
Embed path planning in your product without building a path planner. Your backend sends a boundary and requests a launch link. Launch Pad opens already signed in on that field, in a new window or in an iframe inside your UI. Your user plans in Launch Pad's route editor and the finished path plan comes back to your product. The hard part, a full path planning and route editing interface, is never your problem.
Identity and sessions, the planning and route editing interface, plan storage and exports, and consolidated billing under your partner account.
Ag platforms, FMIS and dealer tools that want path planning inside their product quickly, without owning a route editor. The same API key carries over if you later go deeper.
Your UI, our planning engine. You call the Launch Pad REST API directly: send a boundary and planning parameters, get the path plan back as data, and show it to your users in your own interface. On paper this looks like the easy option. In practice it asks the most of your product. You need your own mission planner or FMIS that can pick sensible defaults, visualize a path plan and route, and hand it to a machine.
The path planning and route optimization itself, boundary handling and corrections, plan storage, and exports in industry formats.
Ag robotics and autonomy platforms that consume routes programmatically, and FMIS vendors that already have a field-operations interface.
Be realistic about the surface area. A route editor is a product in itself. If you do not already have a mission planner that can visualize and dispatch routes, One-Click Launch gets you live far sooner, and you can add direct API calls later with the same key.
Launch Pad inside your FMIS as if it were built there. Your design system, your navigation, your workflows, your sign-in. We scope it together and build it as a joint project. Path planning from a specialist provider already ships this way inside the farm management software of major equipment manufacturers, embedded so deeply that users never notice a third party is involved.
Contact Us to Scope ItWhatever we agree in scoping. Typically the host interface and the identity handshake. Verge builds and maintains the embedded planning components.
Everything under the surface: planning, optimization, storage, exports and the embedded components themselves, kept current as Launch Pad evolves.
OEMs and large FMIS vendors that want path planning as a native, differentiating part of their platform.
The same questions, answered for each option.
| Question | 1. White Label | 2. One-Click Launch | 3. API Integration | 4. Enterprise |
|---|---|---|---|---|
| Code you write | None | A handful of server-side REST calls | A full integration: UI, visualization, sync | Joint project, scoped together |
| Where users plan | In Launch Pad, under your brand | In Launch Pad, opened from your product | In your interface | In your interface, fully native |
| Boundary comes from | Machine connections or file upload | Your product, pushed through the API | Your product, sent with each request | Your product |
| Path plan returns by | Export from Launch Pad | File import, webhook push or pull | API response or webhook | Custom push into your APIs |
| Sign-in | Launch Pad account | Provisioned and signed in by your backend | Your app; server-to-server key | Single sign-on, OpenID Connect |
| Branding | Your logo and subdomain | Companion window, or iframe with your theme | Entirely yours | Entirely yours |
| Billing | One partner bill | One partner bill | One partner bill | One partner bill |
| Best for | Dealers, agronomy services, resellers | Ag platforms and FMIS without a route editor | Ag robotics and FMIS with a mission planner | OEMs and large FMIS vendors |
The options build on each other in practice. The API key you use for One-Click Launch is the same one you use for deeper API calls, and an Enterprise build starts from both.
No engineers to spare for this?
Start with White LabelHave engineers, but no route editor or mission planner of your own?
Start with One-Click LaunchAlready have a mission planner that can visualize and dispatch routes?
Go straight to the APINeed it to be indistinguishable from your own product?
Talk to us about EnterpriseA single admin identity holds your API key and sees usage, plans and per-user activity across every customer you onboard.
You are the billed party, with volume pricing agreed up front. Your customers never see credits or invoices.
Boundary correction on the way in. Path plans out in ISOXML, Shapefile, KML or partner-specific formats.
The same documented API behind every option, with a developer portal and a live demo you can read the source of.
Tell us what your product does and who uses it. We will suggest the option that fits and walk through onboarding, return paths and billing together.