AI Agent Automation Platforms
TinyFish Enterprise: who do I contact for SSO, audit logs, and running in our VPC/on-prem?
6 min read
For SSO, audit logs, and VPC/on‑prem deployment, you’re squarely in TinyFish Enterprise territory—and the right path is to talk directly to the sales and solutions team so they can scope security, governance, and deployment details with you.
Quick Answer: For SSO, audit logs, and private VPC/on‑prem deployment, contact the TinyFish Enterprise team via the “Contact Sales” / “Talk to Sales” path or through your existing TinyFish account rep. These capabilities are part of Enterprise plans and are set up in coordination with TinyFish solutions engineering.
Frequently Asked Questions
Who do I contact to enable SSO, audit logs, and VPC/on‑prem deployment?
Short Answer: Reach out to the TinyFish Enterprise team via the “Contact Sales” / “Talk to Sales” flow on tinyfish.ai or through your current account manager if you already have one.
Expanded Explanation:
SSO, granular audit logs, and running TinyFish in your VPC or on‑prem aren’t toggle-on features; they’re enterprise-grade capabilities that require coordination across your security, infra, and data teams. TinyFish handles these through Enterprise engagements so they can align on identity providers, logging requirements, network boundaries, and any compliance documentation (ISO, SOC 2 timelines, DPIAs, etc.).
Once you submit an Enterprise inquiry, you’ll typically be connected with a combination of sales, security, and solutions engineering. They’ll walk through your requirements (IdP, log sinks, VPC topology, data residency) and propose a deployment and governance model that fits your environment.
Key Takeaways:
- Use “Contact Sales” / “Talk to Sales” for any SSO, audit logging, and VPC/on‑prem deployment requests.
- Existing customers can go straight through their account manager or TinyFish support to kick off Enterprise scoping.
How does the process work to get SSO and audit logging set up?
Short Answer: You’ll go through an Enterprise onboarding process: requirements scoping, security review, then environment configuration and testing.
Expanded Explanation:
Enterprise identity and observability aren’t one-size-fits-all, especially when agents are running sensitive workflows behind logins and portals. TinyFish treats SSO and audit logging as part of a broader governance rollout. After you contact the Enterprise team, they’ll map your identity stack (Okta, Azure AD, Google Workspace, etc.), define role and permission models, and align on how you want run history, screenshots, and step-level events logged.
Audit logs are wired to track who did what, when, and where—API keys, agent definitions, executions, and any changes that affect production workflows. In parallel, SSO integration ensures only the right people can view or modify agents, access the Workbench, or rotate credentials. All of this gets tested in a lower environment before you roll into production.
Steps:
- Initiate contact: Submit an Enterprise request via “Contact Sales” / “Talk to Sales” or through your account rep, flagging SSO + audit log requirements.
- Security & infra scoping: TinyFish and your team align on IdP, SSO protocol (e.g., SAML/OIDC), logging targets, permissions, and compliance needs.
- Configure & validate: TinyFish configures SSO, sets up audit logging and access controls, runs joint testing, and then promotes the setup to production.
What’s the difference between standard TinyFish access and Enterprise features like SSO, audit trails, and VPC deployment?
Short Answer: Standard access focuses on running Web Agents in TinyFish’s managed cloud, while Enterprise adds SSO, granular audit trails, and options to run in your own VPC with advanced security and compliance controls.
Expanded Explanation:
TinyFish’s core offering—serverless Web Agents that navigate/authenticate/extract/transact across sites—is available out of the box on the managed platform. You get the Workbench, API, and concurrency without touching browsers, proxies, or LLM infrastructure. For many teams, that’s enough to replace brittle scrapers and manual ops.
Enterprise builds on that with deeper control and governance: single sign-on, granular permissions, full audit logs, and the ability to deploy TinyFish in your VPC under your rules. You still get the same execution engine and real-time structured outputs, but with security posture and observability that match regulated or large-scale environments.
Comparison Snapshot:
- Standard (Managed Cloud): TinyFish hosts everything; you use SSO-optional access, default logging in the Workbench, and shared infrastructure tuned for multi-tenant reliability.
- Enterprise: Adds SSO integration, granular audit logs, advanced security/compliance, and optional private deployment in your VPC or on‑prem.
- Best for: Teams with strict infosec requirements, regulated data, or large-scale operations that need tight governance and network control.
What does it take to run TinyFish in our VPC or on‑prem?
Short Answer: You’ll need an Enterprise agreement plus collaboration across your infra, security, and data teams to design a private deployment that uses TinyFish’s agents inside your network perimeter.
Expanded Explanation:
Private deployment is for organizations that want TinyFish’s Web Agents but require traffic and data to stay inside their own cloud or data center. Instead of treating TinyFish as a pure SaaS endpoint, you deploy the platform into your VPC so agents run “on your turf” while TinyFish manages the agent engine and updates.
This model gives you network-level control (VPC peering, security groups, private subnets) and the ability to align with internal controls around outbound connectivity, key management, and data retention. TinyFish’s Enterprise team will work with you on architecture (regions, sub-accounts, HA/DR), encryption (AES-256 at rest, TLS 1.3 in transit), and integration with your logging and monitoring stack.
What You Need:
- Enterprise engagement: To access private deployment, custom concurrency, and advanced security/compliance configuration.
- Infra & security ownership: Cloud/VPC access, network/security engineering, and logging/monitoring endpoints to integrate TinyFish with your existing stack.
Why should we involve the Enterprise team instead of just “turning on” SSO or logs ourselves?
Short Answer: Because you’re running production-critical agents behind logins and paywalls, you want identity, auditability, and deployment wired correctly once—not patched together and fragile.
Expanded Explanation:
When Web Agents are hitting carrier portals, checkouts, or internal tools, the failure modes aren’t theoretical—they’re broken quote flows, missed price changes, or untraceable actions. That’s exactly where SSO, granular audit trails, and private deployment matter most. TinyFish’s Enterprise team is built for that reality.
They help ensure the platform runs unattended in the cloud or your VPC with the governance you’d expect from any mission-critical system: SSO instead of shared passwords, AES-256 at rest and TLS 1.3 in transit, zero plaintext storage, and a complete audit trail for every operation. In other words, you’re not just “connecting a login”; you’re putting a web data operations platform into the same trust model as your core infrastructure.
Why It Matters:
- Operational safety: Identity, permissions, and audit logs make every agent action traceable and reviewable—essential when agents touch sensitive workflows.
- Compliance & trust: Enterprise deployment, encryption, SSO, and logging align with ISO 27001:2022 and SOC 2 timelines, keeping infosec and regulators comfortable as you scale.
Quick Recap
If you’re asking about SSO, detailed audit logs, or running TinyFish in your VPC/on‑prem, you’ve crossed into Enterprise territory. Those capabilities sit alongside advanced security, compliance, and custom concurrency. The right next move is to talk directly with TinyFish’s Enterprise team so they can align on your IdP, logging, and deployment requirements and design a setup that can run unattended in production.