You want primitives, not someone else's use case.
Product teams want a governed runtime, agents that respect user permissions, an SDK that fits the stack, and a way to ship to users without a long procurement cycle.
For product and platform teams: a React SDK to embed agents, Computer and Application assets to host what you build, and code you can push to GitHub anytime.
Embed the agent in your product. Host the app on our computer. Own the code.
“It's good to understand the capability of the platform. That how far, and how quickly you guys can get these things going [...] that has been impressive overall.”
“Lets us get a lot more out of our data than [...] We can sit on top of all of the data in [our data warehouse] as opposed to just, like, our little ingested, you know, three gigabytes semantic models. I think we have a lot of power here.”
“Gave Athena the spreadsheet, explained which column I was trying to figure out, and then ten secs it told me... exactly how the calculation was based on the other data.”
“He wrote the entire stuff. By itself. And I was there, and I was thinking, alright. If I had to write all this stuff, I mean, I would've spent days, days, days.”
“I send that to the programmer and he said, alright. I read your file. I copied the section of the code because he has the right interface, and it works. Wow. Just like magic.”
“One workspace. All different, let's say, avatars of their output data. Right? Suddenly, it's dashboard. Excel is here. PowerPoint is when it's all together. It's very impressive.”
“Use the Athena platform probably closer to the concept and how it was designed, like, with the spaces architecture where you've got a set of primitives and capabilities, and you bring together the right set of capabilities to solve a task.”
“Digital worker, it gets spun up, it gets given access to the toolkits that it needs. It gets given access to the data that it needs. Just exists for the period it needs to exist to perform the task. And then it gets torn back down again afterwards.”
“I like that direction, that concept of the agent is the agent. It becomes an entity in its own right with its own ownership and its own missioning, and you get rid of the gray area and the blurry lines.”
“It was PowerPoint... there was no kind of distinction between the two. So that was killer. And I literally had a meeting on it today, and people said how great it was.”
Verbatim from customer calls. Customers anonymized.
Product teams want a governed runtime, agents that respect user permissions, an SDK that fits the stack, and a way to ship to users without a long procurement cycle.
The SDKs and connector tools evolve quickly. Your team can file issues and shape what comes next.
Applications need versions, staging, rollback, and access by directory group, on your brand and domain.
The React SDK puts Athena assets and chat inside your own application, with citations back to your data.
Applications your team builds run on Computers and are published with versions, staging, rollback, and directory-group access.
The code is yours. Push it to your own repository at any time.
Deploy in your VPC, on-premises, or air-gapped, with your own model keys and no standing vendor credentials.
Agents write, review, resolve conflicts, and merge, with every run logged and a human approving the steps you mark.
Where integrations are not allowed, a governed, recorded browser session with authorized credentials.
A branded assistant for every employee, with each person's permissions and single sign-on.
Tools that replace spreadsheets and one-off scripts, published to the teams that need them.
An agent interviews stakeholders, scores options against their criteria, and writes the recommendation with interview excerpts as citations.
Adoption paths assessed against your teams' needs, with sources for every recommendation.
A ten-person pilot with a login most people forgot. A Fortune 500 retailer needed an internal AI assistant that scaled to 10,000 employees, used their own domain and brand, and inherited permissions from their identity, email, document, and chat systems.
Built the portal as an Application with the company's own name and domain. Provisioned by directory group. Each user's Outlook, SharePoint, and Teams permissions inherited live. Saved runs and a proactive daily agenda so it is sticky on day two. The IT lead took the per-seat assistant out of the running with 500 prepaid licenses on the shelf.
The company's own internal product, rolling to 10,000 employees, included in Athena services. White-labeled completely: your brand, your domain, your SSO. No Athena branding unless you want it. Connect the boring systems first.
A portal is only as good as what is connected behind it. Connect the boring systems first.
Build with the tools your engineers already use, deploy in our cloud or yours, and export everything.
VPC on GCP, Azure, or AWS; on-prem; air-gapped. Zero standing vendor credentials. Just-in-time access, logged twice. Hard budgets cap the cost of any retry loop.
VPC on GCP, Azure, or AWS; on-prem; air-gapped. Bring your own model keys. Zero standing vendor credentials.
Just-in-time, time-bounded access requested per incident, approved by the customer, expiring automatically, logged twice: once by the platform, once by the cluster.
A public API with hard budgets. Hard budgets cap the cost of any retry loop. Every run logged. Every step attributable.
The same permission model whether a human or an agent is calling. Each user's Outlook, SharePoint, and Teams permissions inherited live.
Your brand, your domain, your SSO. No Athena chrome unless you want it. Export code to your GitHub at any time.
Every save stamped with the author, human or agent, plus the session and message that caused it. Roll back one range. Keep the rest.
Yes. Build on Computers, publish as Applications with versions, staging, rollback, and directory-group access, on your own brand and domain.
Yes. Deploy in your VPC, on-premises, or air-gapped. Vendor access is just-in-time, approved by you, and logged.
Yes. The React SDK embeds Athena assets and chat in your product, and you can export the code to your own repository at any time.
Start with one application or workflow in a pilot, measured against the criteria your stakeholders set.
Carry engineering, operations, and internal work: writing and reviewing code, investigating incidents, and powering internal tools and assistants. Your product teams can also embed agents in what you ship.
Yes. Use the SDKs and APIs to embed agents in your products, and keep the code in your own repository.
Yes. In your cloud, on-premises, or air-gapped, with your own model keys.
You choose which steps need a person, every run is logged, and production access is time-bounded and approved.
With one internal workflow or tool that engineers keep putting off, delivered to real users with versions and rollback.
Records every change by a person or an agent, rolls back one contributor's edits without losing anyone else's, and keeps the model, instructions, and sources behind each agent action.
How the platform is deployed: Athena's managed cloud, your cloud on AWS, GCP, or Azure, on-prem, air-gapped, or GovCloud. Same platform in every option.
Build, Work, and Data on top; 150+ connectors and every surface in and out; one map of the whole platform.
Ready-made briefs you can run on a schedule.
Bring one product surface or internal tool. We will embed Athena and show it working with your users' permissions.