Enterprise Addienator
Addienator for teams with an organization-controlled AI connection.
Enterprise retains the Pro capability set while your organization controls the provider route, credentials, and approved model mappings. Pricing is private and sales-assisted.
Enterprise inquiries are open
Use the dedicated Enterprise form below. It does not accept registration or payment. Keep passwords, API keys, other credentials or secrets, payment-card information, and confidential source materials out of your inquiry. Enterprise pricing remains private.
Enterprise Inquiry
Ask about private Enterprise access and an organization-controlled AI connection.
What Enterprise changes
Keep the product workflow. Control the organization connection.
Team members use the Addienator workflow through a protected launcher while your organization governs the AI route and provider account.
Complete Pro workflow
Use interactive outline control, Assessment, on-the-job training (OJT), Course Redesign, per-stage Word round trips, and optional Express control.
Organization-controlled connection
Your organization configures and hosts the proxy, keeps provider credentials there, and maps the approved models used for Addienator requests.
Organization account access
Organization membership rules determine which eligible members can open the protected Addienator launcher and its private organization settings.
Enterprise connection
A controlled route from your team to your provider
1
Choose the provider path
The reference proxy includes paths for Gemini API, Gemini on Vertex AI, Azure OpenAI, and compatible OpenAI-style gateways.
2
Host the proxy
Run the reference proxy in an approved Node 20 or later environment or a Cloudflare Worker environment, or implement Addienator Proxy Protocol 1.1 in another stack.
3
Verify the deployment
Run the packaged contract suite and browser self-test before the route is treated as supported. Repeat them after relevant provider or proxy changes.
4
Use the approved route
Eligible members open Addienator through the protected launcher. AI requests then use the organization’s configured route.
Provider credentials stay with the organization
Provider credentials remain in the organization-hosted proxy and are not sent to Addienator or team-member browsers.
AI traffic follows the organization route
Documents, prompts, and model output travel between the team member’s browser, the organization proxy, and the configured provider. Addienator is not in that AI data path.
Provider use is separate
The organization uses its own provider account and remains responsible for its provider configuration, retention settings, and separate usage charges.
See how Addienator supports the work
Review the path from raw materials to an editable design package, then compare the public plan structure.
