Frontier research organisations
National labs, top-tier academic groups, frontier-research foundations. Organisations whose workload pushes the model into regimes it has not yet seen in production.
Business · Frontier
For organisations building at the edge.
Frontier is the engagement model for the small number of organisations whose work pushes Aether into regimes it has not yet shipped. Paired senior research engineer, pre-release roadmap access, dedicated compute, custom training runs, and direct contribution to the next-generation development of the platform.
6–10
global Frontier engagements at any time
6–9 mo
pre-release roadmap access window
12–24 mo
typical engagement length
1:1
paired senior research engineer
What Frontier includes
Six things you cannot buy another way.
The standard Enterprise tier covers most of what large customers need. Frontier adds the parts that depend on real Apex research-engineering time, and that we can only offer to a small number of customers at a time.
Paired research engineer
A named senior Apex research engineer paired with your team for the duration of the engagement. Embedded, not on-call. Authority to commit Apex engineering effort.
Pre-release roadmap access
Access to in-development checkpoints six to nine months before they reach the GA channel. Includes the post-1.5 architecture experiments and the civilisational-scale model variants.
Custom training runs
Dedicated training-compute allocations for custom fine-tunes, domain extensions, and rare-event corpus injections. Scoped to your data, in your tenant.
Reserved inference compute
Dedicated inference-capacity slice, pinned to your workload. No queue contention at peak load; predictable per-call economics.
Direct contribution to Aether
Joint research with the Apex team on the parts of Aether that matter for your discipline. Findings published with you as co-author when the work warrants it.
Public-figure red-team
Frontier customers participate in the external red-team programme — both as adversaries against their own deployment, and as observers against the broader release pipeline.
Who Frontier is for
Four kinds of customer.
The engagement is selective. The fit is technical — Frontier customers are the ones whose workload itself moves the platform forward.
Lighthouse enterprise customers
A handful of enterprise customers per industry whose deployments meaningfully shape the next generation of Aether — typically retiring multi-million-dollar incumbent stacks and pushing the platform's discipline-specific surface.
Sovereign-research consortia
Multi-institution consortia running export-controlled or classified work that requires sovereign deployment and customer-extended refusal corpora.
Civilisational-scale partners
Organisations working on climate, pandemic preparedness, fusion, food security — problems where the commercial-customer pricing model is the wrong fit but the work is foundational to where AI for the physical world has to go.
The deal — both directions
What we commit. What we ask of you.
Frontier is a two-way engagement. We give the customer the access and the attention; we ask the customer for the technical engagement and the willingness to operate on the edge of what is ready.
From Apex
- A named senior research engineer who is yours for the duration. Not a rotation; not an account manager.
- Quarterly roadmap-review sessions with the Aether technical leadership.
- Pre-release checkpoints six to nine months before the GA channel. Distributed under the customer's MSA; not redistributable.
- Dedicated training-compute and inference-compute allocations, scoped in writing.
- Joint publication on the research that emerges from the engagement, attributed appropriately.
- First-look at architecture experiments — including the failures.
From the customer
- Direct, technical pairing with the research engineer. The customer's senior staff is part of the work, not delegated to junior engineers.
- Constructive engagement with pre-release checkpoints — bug reports, failure-mode characterisation, willingness to operate on something that is not yet GA.
- Confidentiality where it applies. The MSA defines the boundary; the customer respects it.
- Willingness to be a reference for other Frontier prospects after the first six months of the engagement.
- Participation in the external red-team programme where relevant to the customer's workload.
What Frontier is not
What it does not mean.
We are deliberate about the engagement model. Frontier is not a re-branded Enterprise tier with extra discounts; it is not unlimited; it is not for everyone large.
- 01
Frontier is not the standard Enterprise tier with extra goodies. The standard Enterprise tier covers VPC, on-prem, sovereign deployment, custom fine-tunes, forward-deployed engineer, 24×7 SLA — that's the right answer for most large customers.
- 02
Frontier is not a path to lower pricing. The commercial terms are typically higher than standard Enterprise, not lower; the value is in the engagement model, not in the line items.
- 03
Frontier is not an early-access discount. We do offer pre-release access; we do not offer it at a discount.
- 04
Frontier is not unlimited. We can support a small number of Frontier engagements at any time — typically six to ten globally — because the engineering effort is real and not infinitely scalable.
Engagement flow
How an engagement actually starts.
The path from first conversation to active engagement. Six to twelve weeks typical, longer for sovereign deployments and where customer-side procurement is heavy.
- 01
Initial conversation
First call is technical, not commercial. The Apex research lead spends an hour with the customer's technical principal to understand the work and the fit.
- 02
Scoping
Two-week scoping with a research engineer paired in. We define what the engagement will produce and what success looks like, in writing.
- 03
MSA + access
Commercial terms and the supplementary Frontier addendum to the MSA. Pre-release checkpoints become available; dedicated compute is provisioned.
- 04
Engagement
Twelve- to twenty-four-month engagement with quarterly technical reviews, monthly roadmap syncs, and continuous pair work between the research engineer and the customer.
- 05
Joint output
Research publications, customer case study (if appropriate), and integration of the work into the public roadmap as the customer permits.
Apply
Write to frontier@apexworldlabs.com.
First message is short: who you are, the workload that brings you here, and what you are trying to do that the standard tiers do not currently support. We reply within one business day. Decisions on a Frontier engagement take between two and six weeks from the first call.
Not sure if it's a fit?
Write to hello@apexworldlabs.com. We will tell you honestly whether Frontier is the right engagement for your work, or whether the standard Enterprise tier serves you better.