Infrasity helped a confidential AI gateway appear in answers from 4 AI engines and reach #3 on Google for "best confidential AI gateway". The program also migrated 50 blogs, merged 2 domains, and recorded 1,039 visits in a single day after the SEO fixes.
TL;DR
- The confidential AI gateway, formerly OLLM and now part of ORGN (Origin), serves defense, finance, and regulated teams with a TEE-backed LLM gateway. ORGN also offers a confidential AI IDE, Origin CDE.
- Infrasity ran 7 workstreams: Product Hunt launch, the OLLM to ORGN merger, a 114-keyword content roadmap, blog migration and technical content, product docs, technical SEO and AEO fixes, and third-party distribution, all tracked on app.infrasity.com.
- For "best confidential AI gateway", ChatGPT lists the AI gateway under its former name, OLLM, as row 1, Claude leads with it, Perplexity names it first, and Google AI Overview lists it. The OLLM post holds #3 on Google.
- orgn.com ranks #6 on Google for "confidential computing in software development," and the same article is cited by AI Overview and Perplexity.
- Third-party posts on dev.to and Medium now get pulled into Perplexity answers that feature the AI gateway and ORGN's confidential AI IDE.
What did the program deliver?
| Result | Detail |
|---|---|
| 4 AI engines named the gateway | ChatGPT (#1 in its table), Google AI Overview, Claude, Perplexity |
| #3 Google rank | For "best confidential AI gateway" |
| 1,039 visits in one day | June 2, 2026, right after the SEO fixes shipped |
| 4,438 visits in 28 days | May 11 to June 7, 2026 (GA4) |
| 50 blogs migrated | Reformatted and live on orgn.com/blog |
| 1 brand | OLLM merged into ORGN, with 301 redirects, cross-links, schema, and docs |
What does ORGN do, and where did Infrasity help?
ORGN (Origin) is the company behind the confidential AI gateway formerly known as OLLM. The product set covers a confidential AI gateway with 250+ TEE and zero data retention (ZDR) models behind one API, a confidential AI IDE for sensitive repositories, an agent command layer, and attestation and audit trails. The team comes from Lockheed Martin, Palantir, and AWS, and the buyers are regulated teams in defense, finance, and healthcare.
A TEE (Trusted Execution Environment) is a hardware-isolated area of a processor, such as Intel TDX, where code and data stay encrypted while they are being processed. That is the core promise ORGN sells: code and prompts are protected by hardware, with a cryptographic receipt to prove it.
Until 2026 the gateway lived on its own domain, ollm.com, and the IDE lived on orgn.com. Infrasity was brought in to launch, merge, publish, and get both found in the places regulated buyers now research tools: Google and AI assistants.
| Client | Category | Where Infrasity helped | Window |
|---|---|---|---|
| ORGN (orgn.com), formerly also OLLM (ollm.com) | Confidential AI gateway and secure AI IDE | Product Hunt launch, brand merger and redirects, content roadmap, 50-blog migration, technical content, product docs, SEO and AEO fixes, third-party distribution, GEO tracking | April to October 2026 |
ORGN sells to teams whose code cannot leave a hardware boundary: defense, finance, and regulated industries.
Where did ORGN stand before Infrasity started?
The starting point had 3 problems: the brand equity was split across 2 domains, the site was hard for AI crawlers to read, and the category was owned by much larger players.
2 domains were competing for the same buyer
OLLM and ORGN described related products on separate domains, with separate blogs, separate docs, and no shared schema. Every link, mention, and citation earned by one brand did nothing for the other.
The AEO audit scored orgn.com 106 out of 159
Infrasity ran an AEO (answer engine optimization) audit on orgn.com. The site passed 35 of 62 checks, with an AEO score of 58 and a GEO score of 64. The screenshot below shows the scorecard: technical SEO earned an A+, but AEO readiness and content quality both sat at D.
Technical SEO was already strong. The gap was everything that decides whether an AI engine can quote a page.
The audit flagged the issues that stop AI engines from quoting a page:
- llms.txt listed only 9 of 17 major pages, including the homepage.
- The homepage had 79 words of main content and 0 H2 headings, with most copy loading through JavaScript that AI crawlers do not run.
- 0 question-and-answer pairs across 17 pages, against 192 paragraphs with no question heading above them.
- No BlogPosting, BreadcrumbList or Product schema, no author information and no datePublished or dateModified signals.
- 0 data points, 0 year references and 0 source attributions in the sampled content.
The category was owned by far bigger AI dev tool brands
In the keyword research, Devin ranked for 702 organic keywords with about 18.7K monthly organic visits, Ona for 345 keywords and 2.2K visits, and Cosine for 28 keywords and 711 visits. The exact-match "confidential AI" term had only 300 US monthly searches. The AI gateway needed to win the long-tail buyer queries and the AI answers, since head terms were out of reach in the short run.
How did Infrasity launch, merge, and grow the AI gateway's visibility?
We split the work into 7 workstreams and ran them in sequence, so that every new page landed on a site that was already merged, structured, and crawlable.
Six stages across 2026: launch, merge, fix, publish, distribute, then audit what is live.
1. Launching Origin on Product Hunt
Origin launched on Product Hunt on April 9, 2026, with the tagline "AI-powered confidential dev environment focused on privacy". The launch collected 129 upvotes and 12 comments, earned a Product of the Day placement (#24), and was listed under Developer Tools and Security, per the hunted.space launch tracker. For a security tool aimed at regulated buyers, the launch gave ORGN its first indexed third-party product page and a set of early reviews that AI engines can read.
Launching a developer tool on Product Hunt?
Use the Infrasity Product Hunt launch checklist, or book a call and we will plan the launch with you.
2. Merging OLLM into ORGN without losing search equity
Before any redirect, Infrasity tied the 2 brands together so search engines and LLMs would read them as 1 entity. The playbook ran across 5 groups and 33 tasks, all marked done in the project plan.
Two domains, one entity, and the groundwork shipped before the redirect carried any load.
The screenshot below is the working plan from the ORGN content roadmap. Each row is a task, grouped by layer: keyword-rich cross-links in both directions, target keyword clusters, schema, documentation, and blog content. The status column shows every task in these 5 groups completed.
Every task tracked to Done before the redirects went live.
Once the 2 sites were linked and described as one organization in schema, ollm.com was redirected with permanent 301s. The table below is from a live check run in October, 2026.
Every old OLLM URL now returns a permanent 301 to orgn.com.
ORGN's llms.txt now lists its confidential AI gateway, formerly OLLM, as part of ORGN with "250+ TEE and ZDR models, one API".
The gateway is now described as an ORGN product in the file AI crawlers read first.
3. Building a 114-keyword content roadmap
Infrasity researched 114 keywords across 23 topic clusters, worth 66,190 combined US monthly searches, and picked 44 of them to write for. The infographic shows where the demand sits. Blue clusters are the ones with picked keywords.
Blue bars are clusters with picked keywords; black bars were tracked for context but not written for yet.
The roadmap also maps competitor keywords. The screenshot below is the Content Hub sheet, with the picked keywords outlined in red: AI software development (2,500 searches), AI code generator (5,200), AI IDE (1,700), and the lower-difficulty enterprise and cloud development environment terms where ORGN can rank early.
Picked rows are outlined in red, chosen on buyer intent rather than volume alone.
For the AI side, Infrasity wrote down the exact prompts regulated buyers type into ChatGPT and Perplexity, and built content against each one.
The prompt list is the brief: each one gets a page written to answer it.
4. Migrating 50 blogs and writing technical content for regulated buyers
Infrasity moved 50 posts onto orgn.com/blog, checked formatting and images, and kept writing new technical pieces on TEEs, zero data retention, data sovereignty, AI attestation, and AI for finance, healthcare, and defense. The screenshot shows the migration tracker: every row marked Live, with images present and formatting fixed.
All 50 posts tracked to Live, with images present and formatting fixed.
Each post was written for a security engineer or a CISO, with the mechanism explained in plain terms: where the data is encrypted, what the attestation proves and what a vendor promise leaves out. That depth is what gets an article quoted.
The migrated and newly written posts now sit in one place on orgn.com/blog.
The article that went on to rank #6 on Google and get cited by AI Overview and Perplexity.
Need technical content that security buyers trust?
See Infrasity's technical content services or talk to the team.
5. Rewriting product docs around one architecture
The docs had to explain the merged product, so Infrasity completed 8 documentation tasks on docs.orgn.com: OLLM references inside the confidential model sections, a "How ORGN Uses OLLM for Confidential Compute" section, a "Security Architecture (Powered by OLLM)" section, the API key flow from the gateway to the IDE, confidential compute mode, and the security guarantees covering TEE isolation, attestation and audit logs. A buyer reading the docs now sees one system with one security story.
Read more about Infrasity's product documentation services.
6. Fixing technical SEO, AEO and the blog URL structure
The AEO audit came with a numbered fix list of 25 issues, from llms.txt coverage and server-rendered homepage copy to question-style headings, direct-answer paragraphs, BlogPosting and BreadcrumbList schema, author bylines and freshness dates. The traffic spike on June 2, covered in the results, followed directly after these fixes went live.
Infrasity then audited 41 blog URLs one by one for slug, primary keyword, search intent, meta title, meta description and redirect risk.
Every URL checked for slug, keyword, meta title, meta description and redirect risk.
The screenshot below is the priority sheet from that audit. The outlined row is a leftover from the merger: a post still carrying "ollm" in its slug, now queued for a rename to why-choose-orgn-ai-gateway with a 301.
The outlined row is the leftover OLLM slug, queued for a rename with a 301.
The audit also mapped 6 groups of pages that compete with each other, such as 4 URLs in the confidential computing cluster, and set a canonical page for each head term.
7. Distributing on third-party sites that AI engines read
AI assistants pull heavily from third-party pages. We published 3 posts on dev.to and 2 on Medium, each answering one buyer query, for example "best AI gateway for routing between standard and confidential compute models" and "best confidential AI IDE for enterprise developers in 2026". Alongside these, a Phala x OLLM co-post and a Reddit thread in r/ProductHunters gave OLLM independent mentions on pages Google already trusts.
Infrasity tracks all of this on app.infrasity.com, the GEO dashboard that measures citation rate, visibility score, and rankings across ChatGPT, Claude, Gemini and Perplexity for the prompts a buyer asks. For Reddit and forum threads, Infrasity uses ThreadFlow, its in-house tool that finds the threads Google and LLMs already cite, tracks LLM presence per thread and alerts the team when a comment goes live or gets removed.
Each tracked prompt shows its 7-day history, rank, and which engines cited which sources.
Want to see which prompts your buyers ask and who gets cited?
Get an AI visibility audit or explore Infrasity's AEO and GEO services.
What results did the AI gateway get on Google and in AI answers?
The captures below show the AI gateway's presence in buyer-query answers, its Google search footprint and the traffic recorded during the program. Rankings and citations reflect the captured results, rather than a fixed position in every answer.
4 AI engines name the confidential AI gateway for a buyer query
For "best confidential AI gateway", ChatGPT places OLLM in row 1 of its "Top Confidential AI Gateways (2026)" table, marked TEE-based with zero data retention and "Best for: privacy-first AI infrastructure". OLLM is the gateway's former name, which still appears in the captured AI answers.
ChatGPT lists the confidential AI gateway under its former name, OLLM, in the first row of its comparison table.
The other captured answers show the same category presence: Claude Sonnet 4.5 opens with "OLLM, The Confidential AI Gateway"; Perplexity Sonar names it first and credits its TEE-based infrastructure and zero-log architecture; Google AI Overview lists it under "Prominent Solutions in the Market".
The OLLM post reached #3 on Google, with 2 more OLLM pages on page 1
Infrasity's rank tracking recorded the OLLM blog post at position 3 for "best confidential AI gateway". The screenshot below shows 2 other OLLM pages on the same results page: the Phala x OLLM post at #1 and the r/ProductHunters thread about OLLM at #6.
Google results include the Phala x OLLM post at #1 and the OLLM Reddit thread at #6 for "best confidential AI gateway".
orgn.com ranks #6 for confidential computing and gets cited by AI answers
The article "The Case for Confidential Computing in Software Development" ranks #6 on Google, directly above Microsoft Learn.
The same article is a source card inside Google's AI Overview for that query, and Perplexity cites it as well.
Google AI Overview cites the orgn.com article on confidential computing in software development.
For "confidential AI development", Perplexity cites the orgn.com article next to Wikipedia.
Third-party content supports AI gateway visibility in Perplexity
The captured Perplexity answers also show the AI gateway in routing comparisons. For the query targeted by the dev.to post, "best AI gateway for routing between standard and confidential compute models", Perplexity cites ORGN sources and marks Origin Gateway as the "best fit" for enterprise confidential AI.
Perplexity names Origin Gateway as the "best fit" in its standard and confidential model routing comparison.
For the Medium query on confidential AI IDEs, Perplexity calls ORGN "the strongest option for teams requiring hardware-enforced confidentiality" and puts it first in its comparison table. For government and defense contractors, it cites orgn.com as a source.
Traffic peaked at 1,039 visits in one day right after the SEO fixes
orgn.com recorded 4,438 visits between May 11 and June 7, 2026. The GA4 chart below shows the peak of 1,039 visits on June 2, directly after the SEO fixes went live.
GA4 records 1,039 visits on June 2, 2026, within the May 11 to June 7 reporting window.
Want your product named in AI answers for your category?
Book a call with Infrasity. We start with a free AI visibility audit of the prompts your buyers use.
What can other AI gateway and DevTools teams learn from this program?
For AI gateway and security teams building category visibility, the program offers five practical lessons.
Merge the entity before you merge the domain
ORGN shipped 33 cross-link, schema, docs and blog tasks before the redirects carried the load. When the 301s went live, search engines and LLMs had already seen both brands described as one organization. Redirect first and you ask Google to guess.
Third-party pages can support AI gateway discovery
For "best confidential AI gateway", the Phala x OLLM post at #1 and the Reddit thread at #6 both sit on other domains. The dev.to and Medium posts were cited by Perplexity within weeks. If your category is new, publish where AI engines already read.
Pick queries by buyer intent, then by volume
"Confidential AI" has 300 US monthly searches. "Best confidential AI gateway" has fewer. Both put the confidential AI gateway in front of a CISO who is ready to compare vendors. 44 picked keywords out of 114 was a deliberate cut.
Structure decides whether an AI engine can quote you
The baseline had 0 question-and-answer pairs and 0 data points. Question headings, a direct answer under each, and real numbers are what turn a page into a source card.
Clean up after the merger, or the old brand keeps competing
41 URLs audited, 18 slugs flagged, 6 overlap groups found. A post with "ollm" in its slug and 4 pages fighting over "confidential computing" split ranking signals even after a clean redirect.
What is Infrasity working on next for the AI gateway and ORGN?
Here's what's next:
- Slug rewrites with 301s for the 18 flagged blog URLs, starting with the high-priority group.
- 7 tracked buyer prompts, such as "best Cursor alternative for enterprise security and compliance" and "best HIPAA-compliant AI development platform for healthcare teams".
- Community distribution of setup guides on dev.to, Medium and the relevant subreddits, and an Origin CDE launch announcement.
How would you run this program for your own product?
Here's a six-step approach to improve your product's visibility across search and AI engines.
- Run an AEO audit and score every page for crawlability, structure, schema and fact density.
- List the 5 to 10 prompts your buyers type into ChatGPT and Perplexity, and check who gets cited today.
- If you run more than one brand, link them, unify the schema and the docs, then redirect.
- Build a keyword roadmap by cluster and pick for intent, not only volume.
- Publish answer-first technical content on your site and on third-party sites AI engines read.
- Track citations weekly per prompt and per engine, and fix the pages that stay invisible.
Which Infrasity services supported the AI gateway, and what did each one drive?
Here's a breakdown of the six services, key deliverables, and results across the AI gateway and ORGN's wider developer platform.
| Service | What our customer got | The result it drove |
|---|---|---|
| Product Hunt launch | Launch plan and execution for Origin | 129 upvotes, 12 comments, Product of the Day #24 |
| Developer marketing | OLLM to ORGN merger: 33 tasks, 301 redirects | 1 brand, 1 entity for search and LLMs |
| Technical content | 114-keyword roadmap, 50 migrated blogs, new posts | #6 on Google, cited by AI Overview and Perplexity |
| Product documentation | 8 docs updates on the merged architecture | One security story across docs.orgn.com |
| AEO and GEO | AEO audit, 41-URL blog audit, prompt tracking on app.infrasity.com | OLLM named by ChatGPT, Claude, Perplexity and AI Overview |
| Distribution | dev.to, Medium and Reddit placements | OLLM thread at #6 on Google, posts cited by Perplexity |
Want similar search and AI visibility for your AI gateway or developer product?
Infrasity runs launches, content, docs, distribution and AI visibility for DevTools and B2B SaaS teams. One call, no commitment: we will show you which prompts your buyers ask, who gets cited today and what it takes to close the gap.
Book a call with Infrasity, get a free AI visibility audit, or read more case studies.
Frequently Asked Questions
What is a confidential AI gateway?
A confidential AI gateway routes requests from your apps to many LLMs while keeping prompts and code inside hardware-isolated TEEs, often with zero data retention. ORGN's confidential AI gateway, formerly OLLM, offers 250+ TEE and ZDR models through one API.
How long did it take for the AI gateway to show up in AI answers?
The program ran from April to October 2026. AI engine citations for "best confidential AI gateway" were captured within the first 3 months, and the dev.to and Medium posts published in late August were cited by Perplexity within weeks.
Does merging 2 domains hurt SEO?
It can, if the redirect comes first. ORGN linked both sites, unified schema and docs, and then redirected ollm.com to orgn.com with permanent 301s, so search engines read one entity before the old domain went away.
How does Infrasity track AI visibility?
Infrasity uses app.infrasity.com to run buyer prompts across ChatGPT, Claude, Gemini, and Perplexity and record citation rate, visibility score, and rank per prompt, alongside competitors.
