01 Enterprise search
Months of consultants. Security sold as add-ons.
Rollouts become integration programs before anyone can test whether the search is useful.
In development · early access
Permission-aware search and AI answers with citations — connected to your tools in 15 minutes, not 6 months. Every result respects who's allowed to see what.
A design target for the first release, now being built.
Use cases
Company knowledge
Sources sync with their ACLs, so every result and Answer is filtered by who is allowed to see it.
Retail and commerce
Facets, typed filters, Rules, and versioned Ranking Profiles for catalog search, with A/B testing in the design.
Apps and sites
Versioned /v1 routes, SDKs, and typed filters, with published bundles instead of a usage bill you cannot predict.
AI agents
Hybrid retrieval, reranking, /retrieve, and MCP tools behind the same permission gate as Search.
Same Collections, same permission gate, same API. All four are design targets for the first releases.
The problem
01 Enterprise search
Rollouts become integration programs before anyone can test whether the search is useful.
02 Developer search
Fast prototypes can leave permissions, answer grounding, and cost control as separate systems to own.
How it works
The onboarding path is being designed to get a real Collection from connection to first search in about 15 minutes.
Start with a planned anchor connector: Google Drive, Microsoft SharePoint, Jira, Confluence, Zendesk, Amazon S3, Google Cloud Storage, PostgreSQL, or the web.
The Schema Service samples the content, recognizes its Archetype, and proposes typed fields, facets, and Index Profile defaults for your approval.
Use Search, cited Answers, retrieval, or MCP against the same Collection. Every path crosses the same permission gate.
Planned first
Nine anchor connectors
First-release capability map
Keep permissions, relevance, Answers, and agent access inside one product boundary — with the controls to inspect and change how each layer works.
Designed for early accessConnect without separating security from content
Content, ACLs, users, and groups follow one connector contract, with permission freshness measured and stale access failing closed.
Make access control the shared boundary
The Identity Graph resolves group membership server-side, then Search, Answers, retrieval, and MCP re-check access before content leaves the system.
Start useful before becoming an expert
The Schema Service samples a Source, recognizes its Archetype, and proposes typed fields, facets, and Index Profile defaults for you to confirm.
Tune relevance without surrendering control
Combine lexical and vector retrieval, reranking, typed filters, Rules, and versioned Ranking Profiles behind one engine-neutral contract.
Give people evidence, not confident prose
Every claim-bearing sentence needs a citation. Unsupported claims are removed, and weak evidence produces an explicit abstention instead of a guess.
Give every product the same retrieval layer
Use versioned /v1 routes, typed JSON filters, /retrieve, and MCP tools that inherit the same Query Pipeline and permission gate.
Built around trust
ACLs sync from your sources and are enforced on every result, answer, and agent call — fail-closed, always.
Every AI answer cites its sources, is checked for support before it renders, and abstains when the evidence is weak.
Connect a source, approve the schema we propose, search. The trial is the POC.
SSO, document-level security, and audit logs from the free tier up. Security is the product, not an SKU.
Published prices, predictable bundles, hard caps you set. Never a surprise invoice — and never degraded security.
For developers & agents
One API for search, retrieval, and grounded answers — typed filters, versioned routes, MCP for your agents, and no engine lock-in.
The public contract uses canonical Collection and Schema nouns, typed JSON filters, and /v1 routes. Engine details stay behind the Query Compiler.
curl https://{project}.api.aerosearch.team/v1/collections/help-center/search \
-H "Authorization: Bearer $AEROSEARCH_SEARCH_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "refund policy for annual plans",
"filter": {
"all": [
{"field": "product_area", "in": ["billing", "plans"]},
{"field": "updated_at", "gte": "2025-07-01T00:00:00Z"}
]
},
"limit": 10,
"ranking_profile": "default"
}'import { AeroSearch } from "@aerosearch/sdk";
const of = new AeroSearch({ apiKey, endUserToken });
const res = await of.collection("help-center").search({
query: "refund policy for annual plans",
filter: {
all: [
{ field: "product_area", in: ["billing", "plans"] },
{ field: "updated_at", gte: "2025-07-01T00:00:00Z" },
],
},
facets: { product_area: { limit: 10 } },
});
console.log(res.queryId, res.hits);{
"mcpServers": {
"aerosearch": {
"type": "streamable-http",
"url": "https://{project}.mcp.aerosearch.team",
"headers": {
"Authorization": "Bearer ${AEROSEARCH_SEARCH_KEY}"
},
"tools": ["search", "retrieve", "answer"]
}
}
}Pricing stance
Bundle meters are visible and understandable before usage begins.
Never a surprise invoice, never degraded security.
Company knowledge should not become less searchable as more people use it.
Autocomplete is not intended to become a hidden meter.
FAQ
AeroSearch is being built around source-synced access control lists and a single fail-closed permission gate. The same gate applies to Search, Answers, retrieval, and agent calls. End-user identity is resolved server-side rather than trusted from caller-supplied group claims.
AeroSearch is in development. Join the waitlist for early-access updates, or apply as a design partner if you want to help shape the first release. We are not publishing a release date yet.
The first connector set is planned around Google Drive, Microsoft SharePoint, Jira, Confluence, Zendesk, Amazon S3, Google Cloud Storage, PostgreSQL, and the web. Connector availability will be confirmed with early-access documentation.
The managed service comes first. Customer-hosted deployment profiles are on the roadmap, but they are not available today.
AeroSearch is being designed as one retrieval layer for company knowledge, retail and commerce discovery, search inside apps and sites, and AI agents. Search, grounded Answers, and agent retrieval share one permission gate, the public API stays engine-neutral, and the pricing model is intended to use published bundles and customer-set hard caps.
Waitlist members receive early-access updates. Design-partner applicants may also be invited to product conversations and pre-release testing when there is a fit. Joining does not guarantee a date or access slot.
Email is required. Company and role are optional. We use those fields only to manage early-access communication and design-partner outreach; the privacy placeholder explains the current handling in more detail.
Build the first release with us
Join the early-access list, or email [email protected] to start a design-partner conversation.
No launch-date promises. No customer-logo theater. Just a direct line to the team building it.