Auroranexis

Enterprise is for agencies that need custom limits, tailored onboarding, negotiated plan overrides, or priority support beyond standard self-serve tiers. Submit a request from Settings → Enterprise or Settings → Billing — enterprise arrangements are reviewed by the Auroranexis team and are not instant self-serve upgrades.

Overview

Enterprise arrangements extend Professional and Business capabilities with negotiated limits, feature enablement, dedicated onboarding, and priority support. Enterprise customers typically manage large client portfolios, operate integration-heavy environments, or require compliance and branding configurations beyond standard plan tiers.

Unlike self-serve plan upgrades through Stripe checkout, enterprise onboarding involves a review process. Once approved, plan overrides and support contacts are applied to your workspace and visible in Settings → Enterprise and Settings → Billing.

Enterprise is designed for customer-facing outcomes: higher limits, tailored rollout, and direct support — not internal platform administration. All request, status, and override visibility flows through Settings → Enterprise and Settings → Billing within your workspace.

Purpose

Standard plans serve most agencies well, but some organizations need higher API rate limits, expanded monitoring capacity, additional seats, custom feature combinations, or hands-on migration support. Enterprise exists to accommodate these requirements without forcing agencies into one-size-fits-all tiers.

The enterprise program also provides a direct support channel and agreed response expectations, reducing operational risk for agencies running mission-critical client operations on the platform.

Submitting an enterprise request is the first step. Include specific numbers — client count, seat needs, expected API volume, integration count — so the review team can evaluate your requirements efficiently and propose appropriate overrides.

Core Concepts

Enterprise request — a formal inquiry submitted from Settings → Enterprise or Settings → Billing describing your requirements.
Plan override — a custom configuration applied to your workspace after approval, adjusting limits or enabling features beyond your base tier.
Custom onboarding — a structured rollout including workspace setup, migration planning, and team training.
Priority support — expedited assistance through agreed channels with defined response expectations.
Custom limits — negotiated caps on clients, seats, API rate limits, monitoring targets, automation runs, and other resources.
Account contact — your designated Auroranexis point of contact for enterprise matters.

Features

Custom client, seat, and portfolio limits for large agencies.
Elevated API rate limits for integration-heavy deployments.
Expanded monitoring, automation, and storage capacity.
Feature enablement beyond standard plan tier boundaries.
Dedicated onboarding with migration and rollout planning.
Priority support with agreed response times.
Flexible billing arrangements negotiated outside standard Stripe checkout where applicable.
Plan override visibility in Settings → Enterprise.

What enterprise includes

Enterprise customers receive a combination of custom limits, feature overrides, onboarding support, and priority assistance tailored to their operational profile. The specific package is defined during the review process and reflected in Settings → Enterprise after approval. Standard self-serve checkout cannot provision enterprise-level customizations — the request flow is required.

Step-by-step usage

Submit an enterprise request

Open Settings → Enterprise or Settings → Billing.
Select Request enterprise or the equivalent action.
Provide your agency name, team size, client count, and integration requirements.
Describe specific limits or features you need beyond your current plan.
Submit the request and note the confirmation or reference shown.
Monitor request status in Settings → Enterprise during the review period.

Complete custom onboarding

After approval, your account contact schedules a kickoff call.
Align workspace roles and permissions with your delivery model.
Plan data migration, report templates, and portal rollout phases.
Configure integrations and automation with agreed capacity limits.
Complete check-in sessions to validate the rollout against your requirements.

Verify plan overrides

Open Settings → Enterprise after approval.
Review applied overrides for client limits, seats, API rate limits, and enabled features.
Cross-reference effective limits in Settings → Usage.
Contact your account contact if displayed limits do not match the approved agreement.

Use priority support

Best Practices

Document required limits and features before submitting your request — specific numbers accelerate review.
Identify an internal operations owner who will manage the enterprise rollout and serve as the primary contact.
Plan portal and integration rollouts in phases to avoid overwhelming client contacts during migration.
Review Settings → Enterprise after approval to confirm overrides match your agreement.
Maintain an up-to-date team roster in Settings → Team as your agency grows.
Coordinate billing changes, renewals, or cancellations with your account contact rather than self-serve portal actions when under a negotiated agreement.
Schedule periodic check-ins with your account contact to review usage trends and adjust limits proactively.
Monitor Settings → Usage regularly to identify when approaching custom limits before operations are blocked.

Examples

Marketing agency

An agency operating four sub-brands needs white-label portal configurations beyond the Business tier client limit. They submit an enterprise request from Settings → Billing specifying brand count, portal customization needs, and seat requirements. Approved overrides increase client and portal limits, and onboarding includes branding configuration guidance for each sub-brand.

AI automation agency

An automation agency with high-volume webhook and API traffic submits an enterprise request detailing expected automation runs, integration count, and incident write volume. After approval, custom automation and API limits appear in Settings → Enterprise. The team validates headroom in Settings → Usage before migrating production workflows from a staging workspace.

MSP

An MSP with one hundred fifty clients and twelve integrations needs API rate limits five times the Business tier maximum. They submit an enterprise request from Settings → Enterprise detailing client count, integration list, and expected API call volume. After approval, custom API limits and expanded automation capacity appear in Settings → Enterprise. Priority support contact details are shared during onboarding.

Consultancy

A boutique consultancy growing from forty to ninety clients within one year submits an enterprise request anticipating seat, client, and automation run requirements. Rather than repeatedly upgrading through self-serve checkout, they negotiate a single override package. After approval, limits in Settings → Enterprise accommodate projected growth with a scheduled check-in at the six-month mark.

Enterprise deployment

A compliance-focused agency migrating three hundred client records requests enterprise onboarding with migration support. During custom onboarding, the team helps map report templates, configure role structures, and phase portal rollout over six weeks. Plan overrides enable compliance audit features and expanded storage for historical records.

Troubleshooting

Common enterprise issues

Problem	Cause	Solution
Enterprise request still pending	Review process requires business days for evaluation	Check Settings → Enterprise for status updates; allow time before follow-up.
Limits not updated after approval	Override application may still be in progress	Confirm approval is complete in Settings → Enterprise; contact your account contact if overdue.
Cannot find enterprise contact details	Contact information shared during onboarding email	Refer to the onboarding email or open a standard support request referencing your enterprise status.
Self-serve checkout conflicts with enterprise agreement	Plan changes through Stripe may not reflect negotiated terms	Contact your account contact before making plan changes through the customer portal.

FAQ

How do I request an enterprise plan?: Open Settings → Enterprise or Settings → Billing and submit an enterprise request with your agency details and requirements. The Auroranexis team reviews scope, limits, and timeline before approval.
Is enterprise an instant upgrade?: No. Enterprise is a reviewed process, not a self-serve checkout option. Allow business days for evaluation and onboarding scheduling.
Where can I see my custom limits?: Approved plan overrides and effective limits are displayed in Settings → Enterprise. Cross-reference current consumption in Settings → Usage.
Can I cancel an enterprise subscription through the customer portal?: Enterprise billing may follow a negotiated agreement. Coordinate cancellation or plan changes with your account contact to ensure contractual terms are respected.
What support do enterprise customers receive?: Enterprise customers receive priority support through agreed channels with defined response expectations. Contact details are shared during onboarding.
Do I need to be on Business before requesting Enterprise?: No specific tier is required. Submit your request from Settings → Enterprise with your current requirements regardless of your existing plan.

Need help?

Contact support@auroranexis.com for onboarding support, billing questions, or product guidance. Include your workspace name, the module you are working in, and a brief description of your goal so we can respond efficiently.

Refer to the support contact details shared during onboarding.
Use the agreed channel (email or support portal) for enterprise-priority requests.
Include workspace name, issue description, and impact assessment in your request.
Escalate through your account contact for urgent operational issues.