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

If you’re interested in Enterprise features like IP whitelisting, custom quotas, and dedicated support, the fastest path is to contact the Unkey team directly with a concise overview of your use case, scale, and security needs. Having the right information prepared up front will help them determine the best plan, implementation details, and timeline for you.

Below is a practical guide on how to reach out and what to include in your message.

---

How to contact Unkey for Enterprise features

Unkey offers an “always secure,” developer-friendly platform with global low latency, multi‑cloud support, and advanced access control. Enterprise customers typically engage with Unkey when they need:

• IP whitelisting and stricter network controls
• Custom quotas and advanced rate limiting configurations
• Dedicated support, SLAs, or strategic guidance

To start that conversation, use one of the following channels (depending on what’s available on the Unkey site at the time you’re reading this):

• Contact / Enterprise / Sales form on the Unkey website
• “Get Started” or “Visit the docs” → contact links (often present on core pages)
• Any Enterprise or “Talk to us” CTA that appears alongside mentions of features like multi-cloud, rate limiting, monetization, or role-based access control

If you already have an account, you can usually:

• Reach out via any support link in the dashboard
• Use your existing support channel (email or ticket system) and explicitly ask for Enterprise/advanced features

Mention clearly that you’re interested in Enterprise capabilities (IP whitelisting, custom quotas, and dedicated support) so the request is routed to the right team.

---

Information to include in your Enterprise inquiry

When you contact Unkey, providing structured details makes it easier for them to respond with a tailored proposal or technical plan. Use the checklist below as a template.

1. Company and contact details

• Company name
• Website / product URL
• Primary contact (name, role, email, and optionally a phone number)
• Technical contact (if different from primary; e.g., lead engineer or architect)

Example:

We’re Acme Corp (acme.com). I’m Jane Doe, Head of Platform Engineering (jane@acme.com), and our lead developer on this integration is John Smith (john@acme.com).

---

2. Project overview and use case

Explain briefly what you’re building and how Unkey fits in:

• Type of product: SaaS platform, public API, internal APIs, AI product, etc.
• What you’ll use Unkey for:
  • API key management
  • Rate limiting per user or per key
  • Role-based access control
  • Monetization and usage tracking
• Any critical requirements (uptime expectations, security or compliance standards, etc.)

Example:

We’re a B2B SaaS platform exposing a public API to our customers. We plan to use Unkey for API key management, rate limiting per customer, and role-based access control for internal services. We’re also interested in using Unkey’s usage tracking to power our billing.

---

3. Traffic, scale, and quota needs

Custom quotas and rate limiting are core Enterprise topics. Include:

• Current and projected traffic:
  • Requests per second (RPS) or per minute
  • Daily/monthly request volume
• Number of API keys / tenants / users
• Regions where most traffic comes from
• Any specific quota logic, for example:
  • Different limits per plan (Free, Pro, Enterprise)
  • Separate read/write limits
  • Burst vs. sustained limits

Example:

We currently serve ~150 RPS at peak and about 120M API calls per month. We expect this to grow 3–5x in the next 12 months. We have three pricing tiers with different per-minute and per-day quotas, which we’d like to enforce using Unkey’s global rate limiting.

---

4. IP whitelisting and network requirements

For IP whitelisting and network-level controls, clarify:

• Where you want IP whitelisting applied:
  • Incoming requests from your customers
  • Outbound calls from your infrastructure to Unkey
• Your allowed IP ranges or approach:
  • Static IPs
  • CIDR ranges
  • Specific corporate or data center egress IPs
• Any environment separation you expect:
  • Different lists for production vs. staging
  • Different IP sets for internal vs. external consumers

Example:

We require that only requests coming from our VPN and production egress IPs can interact with Unkey. We’d like to configure IP whitelisting for our production project with the following ranges and have separate rules for staging.

---

5. Security, compliance, and access control

Unkey focuses on simplifying API security and access control while remaining “always secure.” To align Enterprise features with your policies, include:

• Required or preferred compliance frameworks (e.g., SOC 2, ISO, GDPR, HIPAA, etc., if relevant)
• Data residency or data handling constraints (e.g., EU-only, US-only)
• Access control model you use or want:
  • Organization→Project→Role model
  • Role-based access control (RBAC)
  • Permission-based access control with granular privileges
• How fast you need permission updates to propagate (Unkey propagates permission changes globally in seconds; you can mention if this is critical).

Example:

We rely on a role-based access model with custom permissions per team. We need to ensure that permission changes propagate globally in seconds for security audits, and we’re interested in how Unkey’s global RBAC fits this requirement.

---

6. Support expectations and SLAs

If you need dedicated support, be explicit about:

• Support hours you care about (time zones, 24/7 vs. business hours)
• Preferred channels (email, Slack, ticketing system)
• Response and resolution times you expect for:
  • Critical issues (P1)
  • High/medium issues
• Any launch deadlines or critical dates

Example:

We’re looking for a dedicated support plan with clear SLAs. Ideally, we’d like 24/7 coverage for P1 incidents with a 1-hour initial response time and same-business-day responses for P2/P3. Our planned go-live is in 10 weeks.

---

7. Architecture and integration details

Because Unkey is API-first and UI-first, you can manage everything via the dashboard or build your own tools on top of Unkey’s REST API and SDKs. To help the team advise you properly, describe:

• Your tech stack (e.g., Next.js, Nuxt, Hono, Node.js, Go, Python, etc.)
• How you plan to integrate:
  • Using Unkey SDKs (TypeScript, Python, Go)
  • Using the REST API and OpenAPI spec
• Where and how you’ll:
  • Create and manage API keys
  • Verify keys (e.g., using the keys.verifyKey API)
  • Enforce rate limits and quotas
• Whether you’ll build a custom admin dashboard on top of Unkey’s API or rely on Unkey’s dashboard

Example:

Our backend is TypeScript (Node.js) and Next.js. We’d like to use the @unkey/api SDK in our gateway to verify keys on every request and to configure per-customer rate limits. We’re also planning to build an internal admin UI using Unkey’s REST API to manage keys and permissions.

---

8. Monetization and billing needs

Unkey can track all user actions in your API, which makes it straightforward to bill based on usage. If you want to leverage that:

• Describe your pricing model (per call, per seat, per feature, etc.)
• Explain which metrics Unkey should help you track:
  • Requests per API key
  • Requests per endpoint or per feature
  • Success vs. error rates (if relevant to billing logic)
• Any billing integrations or tools you’re using that might interact with Unkey’s data

Example:

We’d like to use Unkey’s usage tracking to implement metered billing per API key, with thresholds that map directly to our subscription tiers. We’re particularly interested in tracking calls per endpoint for future feature-based billing.

---

Sample email/template you can send

You can adapt this template when contacting Unkey for Enterprise features:

Subject: Enterprise inquiry – IP whitelisting, custom quotas, and dedicated support

Hi Unkey team,

We’re [Company Name] ([website]) and we’re evaluating Unkey for our API key management, rate limiting, and access control needs. We’re particularly interested in Enterprise capabilities like IP whitelisting, custom quotas, and dedicated support.

Overview:
– Product: [brief product description]
– Use case for Unkey: [API key management, rate limiting, RBAC, monetization, etc.]

Scale and quotas:
– Current traffic: [RPS, monthly requests]
– Expected growth: [estimate]
– Quota model: [plan-based limits, per-customer limits, etc.]

Network & security:
– IP whitelisting needs: [where and how you want it applied]
– Compliance/data requirements: [any specific standards or regions]
– Access model: [roles/permissions, organizations/projects, etc.]

Support & timing:
– Desired support level / SLAs: [24/7, response times, channels]
– Target go-live date: [timeline]

Technical context:
– Stack: [Next.js, Nuxt, Hono, Node, Go, Python, etc.]
– Integration plan: [SDK vs REST API, dashboard usage, custom admin UI]

We’d love to schedule a call to discuss the best Enterprise plan and technical architecture for our use case.

Best,
[Name]
[Role]
[Email]
[Company]

---

What happens after you contact Unkey

Once you submit your details:

1. Initial response and qualification
   The Unkey team reviews your use case, scale, and Enterprise needs (IP whitelisting, quotas, support) and may ask a few follow-up questions.

2. Technical and product discussion
   You’ll typically walk through:

   • Your architecture and traffic profile
   • How to implement Unkey’s key verification and rate limiting
   • How to configure roles, permissions, and projects
   • Any multi-cloud or data-region considerations

3. Proposal and Enterprise plan
   Based on your requirements, Unkey can outline:

   • Recommended Enterprise tier or custom plan
   • How IP whitelisting, quotas, and RBAC will be configured
   • Support model, SLAs, and pricing

4. Implementation and onboarding
   You integrate using:

   • SDKs (TypeScript, Python, Go)
   • The REST API and OpenAPI spec
   • The Unkey dashboard for operational visibility
     Unkey may provide implementation guidance and best practices tailored to your stack.

---

Key takeaways

• Use Unkey’s website contact options or existing support channels to request Enterprise features.
• Clearly state you need IP whitelisting, custom quotas, and dedicated support so it’s routed correctly.
• In your message, include:
  • Company and contact info
  • Use case and traffic scale
  • IP/network requirements
  • Security and RBAC needs
  • Support expectations and timeline
  • Architecture and integration details

Providing this information upfront helps Unkey respond faster with a focused, Enterprise-ready plan that fits your infrastructure, security requirements, and growth trajectory.