AI Chat UI Toolkits
Assistant-UI Enterprise: who do I contact for SLA/on-prem, and what security info do they provide?
6 min read
For teams evaluating Assistant-UI for production workloads, it’s important to know who to talk to about enterprise requirements—like SLAs, on‑prem options, and security—and what information you can expect to receive during the process.
This guide explains how to contact the Assistant-UI team for enterprise discussions and outlines the typical security and compliance information they can share to help you complete vendor due diligence.
How to contact Assistant-UI for SLA, on‑prem, and enterprise deals
Assistant-UI is built to support both indie developers and large teams, but questions about SLAs, enterprise pricing, and deployment models (including on‑prem or private cloud) are handled directly by the core team.
To start an enterprise conversation, including:
- Negotiated SLAs (uptime, response times, support guarantees)
- On‑prem or private cloud deployment options
- Volume or team pricing
- Security and compliance documentation
you should:
-
Use the “Contact Sales” path
- On the official Assistant-UI site, look for a “Contact Sales” or “Get in touch” option in the navigation or the “Build once. Ready for production.” call-to-action section.
- This routes you to the team that handles enterprise, SLAs, and deployment questions rather than general community support.
-
Include key details in your initial message
To speed up the conversation, briefly share:- Your company name and size
- Expected usage (number of users, environments, or apps)
- Whether you’re interested in:
- Cloud-hosted Assistant UI Cloud
- On‑prem / self‑hosted / private VPC
- Any hard requirements (e.g., SOC 2, data residency, specific SLAs)
-
Ask specifically about “Assistant-UI Enterprise”
If you know you need:- Contractual uptime and support
- Custom integration help (e.g., LangGraph, LangSmith, LangChain, Vercel AI SDK)
- Security review support
reference “enterprise” or “production deployment” in your message so you’re routed to the right person.
What’s included in an enterprise/SLA discussion
When you contact the Assistant-UI team for enterprise needs, you can typically expect a structured conversation around:
-
Use case and architecture fit
How Assistant-UI’s React-based chat components, streaming UX, and state management will plug into:- Your LLM stack (Vercel AI SDK, LangChain, LangGraph, or any LLM provider)
- Your hosting model (cloud vs on‑prem)
-
Service level expectations
This usually covers:- Target uptime and availability
- Incident response and communication expectations
- Supported channels for support (email, ticketing, dedicated Slack, etc.)
- Maintenance and upgrade process for the UI library and any associated cloud services
-
Deployment and integration approach
- How you’ll deploy Assistant-UI in production (bundling with your React app, integration with LangGraph/LangSmith, etc.)
- How Assistant UI Cloud is used (if applicable) for persistent threads and sessions
- Options to limit or avoid external data storage if you prefer self-hosting
On‑premise and self-hosted options
Assistant-UI is an open-source TypeScript/React library, which naturally lends itself to self-hosted and on‑prem deployments:
-
Open-source core
- You can run the UI components entirely within your own infrastructure as part of your React application.
- This model is attractive for teams with strict data residency or network isolation requirements.
-
Assistant UI Cloud vs self-hosted state
- Assistant UI Cloud can render the chat interface and store threads so that sessions persist across refreshes and context builds over time.
- For stricter environments, you can discuss with the team:
- Whether and how to disable or replace cloud-based storage
- Using your own back end or database for conversation state
- Network isolation patterns (private VPC, VPN, etc.)
-
Enterprise/on‑prem support
When you contact the team about on‑prem, expect to discuss:- Supported deployment models (Kubernetes, containerized, or integrated into your own app)
- How updates and security patches are delivered
- Any licensing or enterprise add-ons that differ from the default open-source usage
Security and privacy information you can request
During an enterprise evaluation, the Assistant-UI team can typically provide structured information to help your security and procurement teams complete due diligence. While the exact documents and certifications evolve over time, you can usually request details about:
1. Data flow and storage model
Key questions to ask (and expect clear technical answers on):
- What data does Assistant-UI handle in:
- The open-source React components?
- Assistant UI Cloud (if used) for conversations and threads?
- Where are threads and sessions stored and how long are they retained?
- Does any data leave our environment when we self-host?
- How does streaming output from LLM providers flow through the UI?
Since Assistant UI Cloud powers conversations, streaming output, and persistent threads, you should expect documentation on:
- Storage locations and providers
- Encryption at rest and in transit
- Access controls around stored conversation data
2. Authentication, authorization, and tenant isolation
If you’re using Assistant UI Cloud or any managed enterprise features, ask for:
- How user identity is handled (SSO, OAuth, custom auth, or tokens)
- How threads are scoped to users/tenants
- Any multi-tenant isolation measures and how data between customers is separated
3. Infrastructure and network security
Typical information you can request:
- Hosting providers and regions used for Assistant UI Cloud
- Network protections (firewalls, TLS, secure headers)
- Backup and disaster recovery strategy
- Logging and monitoring practices
If you’re deploying on‑prem or self-hosting only the open-source parts, much of the infrastructure security will be your responsibility—but the team can still clarify:
- Which components are purely client-side
- Which parts (if any) call out to their cloud or third parties
- How to configure the library to avoid external calls if needed
4. Compliance posture and policies
If your organization has compliance requirements, ask the Assistant-UI team for:
- Current or in-progress certifications (e.g., SOC 2, ISO 27001)
- Data processing and privacy policies
- Incident response procedures
- Subprocessor list (for any cloud services involved)
They may also provide a security overview or whitepaper summarizing:
- Architecture diagrams for Assistant UI Cloud
- Data lifecycle and retention
- Access control and internal security practices
How Assistant-UI fits into a secure AI stack
Assistant-UI is designed as a UI and state management layer for conversational AI—letting you focus on your agent logic, security model, and infrastructure controls:
- Works with Vercel AI SDK, LangChain, LangGraph, or any LLM provider, so you can keep your prompts, models, and data inside your existing security perimeter.
- Provides high-performance streaming and stateful multi-turn conversations without forcing a particular back end, making it straightforward to align with your own compliance and data governance standards.
- Many teams pair Assistant-UI with:
- LangGraph for stateful agents and tools
- LangSmith for observability and evaluation
- Their own APIs or private LLM endpoints for sensitive data
When you contact the team for enterprise details, be explicit about your broader AI stack so they can share architecture patterns that match your risk profile.
Key takeaways
- Who to contact: Use the “Contact Sales” / enterprise contact on the official Assistant-UI site to discuss SLAs, on‑prem/self-hosting, and security.
- What to mention: Include your use case, estimated scale, deployment preference (cloud vs on‑prem), and any hard security/compliance requirements.
- What security info to expect:
- Data flow and storage details (including how Assistant UI Cloud stores threads and sessions)
- Infrastructure and network security practices
- Authentication/authorization and tenant isolation model
- Compliance posture and high-level policies
If you share your organization’s requirements clearly in the initial contact, the Assistant-UI team can quickly provide the right security documentation and enterprise options to support a production deployment.