How do I contact Unkey for Enterprise (IP whitelisting, custom quotas, dedicated support) and what info do they need?

For enterprise use cases like IP whitelisting, custom quotas, and dedicated support, you’ll typically work directly with the Unkey team to design a tailored plan that fits your scale, security, and compliance needs. While self‑serve plans are ideal for getting started quickly, advanced requirements are best handled via an enterprise conversation.

Below is how to contact Unkey for enterprise features and what information to prepare so the process is fast and productive.

How to contact Unkey for Enterprise features

To discuss IP whitelisting, custom quotas, or dedicated support, reach out to Unkey through one of the following:

Enterprise / Sales contact form
Visit the Unkey website and look for links such as:
- “Enterprise”
- “Contact sales”
- “Talk to us” / “Get in touch”
These forms are optimized for enterprise requests and will route you to the right person quickly.
Support or help links in the dashboard
If you already use Unkey:
- Log into the Unkey dashboard.
- Look for “Support,” “Help,” or “Contact us.”
- Open a ticket or request “Enterprise / custom plan” directly from your logged‑in account so they can see your current usage.
Developer‑focused channels (for technical scoping)
If Unkey provides a support email or a community/chat link from the docs:
- Use the subject line:
  Enterprise request: IP whitelisting, custom quotas, dedicated support
- Add your workspace or organization name so they can match you to your existing account.

If you’re unsure which path is best, start with the enterprise/contact form on the main site—those submissions are generally monitored by the team that handles custom contracts and enterprise SLAs.

Information to include in your Enterprise request

Providing clear, structured details in your first message helps Unkey assess fit, propose the right configuration, and respond faster. At a minimum, include the following.

1. Company and contact details

Company name (and legal entity if applicable)
Website / domain
Industry (e.g., fintech, SaaS, healthcare, AI platform)
Primary contact:
- Full name
- Role (e.g., CTO, Head of Platform, Staff Engineer)
- Email and (optionally) a direct phone number
Time zone and preferred meeting times for a call

This helps Unkey understand who’s involved and what kind of compliance or partnership expectations might exist.

2. Technical use case and architecture overview

Explain briefly how you plan to use Unkey and what you’re building:

Type of application
- Public API, internal microservices, mobile app backend, B2B SaaS, AI platform, etc.
What you use Unkey for
- API key management and verification
- Global rate limiting
- Role-based access control and permissions
- Usage tracking and monetization
Basic architecture (high level is enough):
- Clouds/providers you use (e.g., AWS, GCP, Azure, multi‑cloud)
- Primary regions (e.g., US‑East, EU‑Central, APAC)
- Whether you plan to call Unkey from backend services, edge functions, serverless, etc.

This aligns with Unkey’s strengths: multi‑cloud support, global low latency, and API-first design.

3. IP whitelisting requirements

If IP whitelisting is a key requirement, be as specific as possible:

What needs to be whitelisted:
- Source IPs / CIDR ranges for your servers or gateways
- Any VPN or corporate egress IPs
Environments:
- Separate lists for production, staging, and development if needed
Direction:
- Inbound restrictions (only certain IPs can call Unkey)
- Outbound restrictions (Unkey should only call certain IPs, if relevant)
Change frequency:
- How often your IPs change (static vs dynamic)
Compliance context (if applicable):
- Any specific regulations driving IP whitelisting (e.g., SOC 2, ISO 27001, financial or healthcare regulations)

Providing a draft IP list (even if it’s approximate) helps the Unkey team quickly confirm feasibility and any limitations.

4. Custom quota and rate limiting needs

Unkey provides simple, configurable global rate limiting that can be customized per customer. For enterprise scenarios, describe:

Expected traffic volume:
- Requests per second (RPS) peak
- Total daily or monthly API calls
Number of API consumers:
- How many customers/tenants you’ll manage keys for
- Rough growth expectations over the next 6–12 months
Quota logic:
- Per‑key, per‑user, per‑tenant, or per‑endpoint quotas
- Whether quotas differ by plan (e.g., “Free,” “Pro,” “Enterprise”)
Rate limit patterns:
- Global vs region‑specific limits
- Burst vs sustained limits (e.g., 100 RPS burst, 1M requests/month)
Monetization model (if relevant):
- How you plan to bill customers based on usage
- Any thresholds that map directly to your pricing tiers

This helps Unkey propose the right configuration for rate limiting and usage tracking, and ensures the underlying infrastructure is sized correctly.

5. Support, SLAs, and security expectations

For dedicated support and enterprise‑grade assurances, clarify what you need:

Support level:
- Business hours vs 24/7 incident response
- Expected response and resolution times for critical issues
Channels:
- Email, ticketing system, dedicated Slack/Teams channel, or on‑call escalation
Security and compliance:
- Any required documentation (e.g., security overviews, data flow diagrams)
- Required certifications or audits, if applicable
Incident handling expectations:
- How you expect to be notified about incidents
- Requirements for post‑incident reports or RCAs

Be explicit about what “dedicated support” means to your team (for example, “We need a named technical contact and a guaranteed response time on severity-1 issues”).

6. Data location, latency, and multi‑cloud needs

Unkey is designed for global low latency and works with any cloud provider. For enterprise, you might have stricter requirements:

Regions and data residency:
- Where most of your users are located
- Any data residency requirements (e.g., “EU data must stay in the EU”)
Cloud providers:
- Which providers and regions you use (e.g., AWS us-east-1, GCP europe-west1)
Latency expectations:
- Any strict latency SLOs you must meet for your own customers

This allows Unkey to align your setup with their global infrastructure and advise on best practices for optimal performance.

7. Access control and organization structure

Unkey supports role-based access control (RBAC) with granular permissions that propagate globally in seconds. For enterprise usage:

Team size and roles:
- How many developers, admins, and operators will access Unkey
Access model:
- Roles you need (e.g., “Owner,” “Admin,” “Billing,” “Read‑only,” “Support”)
- Any separation of duties (e.g., security vs engineering vs finance)
Permission needs:
- Who can create or revoke keys
- Who can configure rate limits or quotas
- Who can view or export usage data

Sharing this up front lets Unkey recommend or configure an RBAC model suited to your organization.

8. Timelines and decision process

Enterprise engagements go more smoothly when the timeline and decision flow are clear:

Timeline:
- When you need the enterprise features live in production
- Any key milestones (beta launch, public launch, compliance audits)
Evaluation stage:
- Are you in early exploration, proof‑of‑concept, or procurement?
Decision makers:
- Who will sign off (engineering, security, procurement, legal)

Mention if you have hard deadlines (e.g., “We need IP whitelisting and custom quotas live within 4 weeks for our public launch”).

Example template you can copy into your message

You can use this outline when you contact Unkey for enterprise features:

Subject: Enterprise request – IP whitelisting, custom quotas, dedicated support

Company: [Name] ([Website])
Industry: [Industry]
Primary contact: [Name, Role, Email, Time zone]

Use case:

We use Unkey for [API key management / rate limiting / RBAC / monetization].

Our stack: [cloud providers, main regions, app type].

IP whitelisting:

We need the following IPs/CIDRs whitelisted: [list or description].

Environments: [prod/staging/dev].

Compliance/security context: [if any].

Custom quotas & rate limiting:

Expected traffic: [peak RPS, monthly requests].

Tenants/customers: [current number, projected growth].

Quota model: [per-tenant, per-key, plan-based, etc.].

Support & SLAs:

Desired support level: [e.g., 24/7 for severity-1 incidents].

Channels: [email, Slack, etc.].

Security/compliance needs: [any specific requirements].

Additional details:

Regions and latency expectations: [regions, SLOs].

RBAC needs: [approx. team size, roles].

Timeline: [target go-live date, key milestones].

We’d appreciate a short call to discuss pricing, technical details, and any requirements on our side.

What happens after you contact Unkey

Once you’ve submitted your enterprise request with the details above, you can generally expect:

Initial response and clarification
Someone from the Unkey team will respond, confirm they received your request, and ask any clarifying questions.
Technical and security review
The team will evaluate feasibility for IP whitelisting, your quota model, and any security or compliance requirements.
Proposed plan and pricing
They’ll share an enterprise plan proposal aligned with your scale, support needs, and feature set.
Implementation guidance
Using Unkey’s SDKs, REST API, and public OpenAPI spec, they’ll help you integrate:
- Key verification and management
- Global rate limiting and quotas
- Role-based access control and permissions
Ongoing partnership
With dedicated support in place, you’ll have a smoother experience as you grow, refine quotas, and introduce new products.

Preparing this information before you contact Unkey for enterprise (IP whitelisting, custom quotas, dedicated support) makes the conversation faster, reduces back‑and‑forth, and helps the team design a secure, scalable setup that fits your exact needs.