Innovexa
Innovexa
Enterprise Support

Questions,
answered.

Everything you need to know about integration, deployment, compliance, and procurement for the Innovexa ORBI platform. Can't find what you're looking for? Our enterprise team is one message away.

01

Integration & identity

How does Single Sign-On (SSO) authentication function across our enterprise team?

Innovexa ORBI supports SAML 2.0 and OAuth2 protocol standards. Network administrators can map Okta, Microsoft Azure Active Directory, or Google Workspace identity profiles directly to system RBAC permissions. Group-to-role synchronization, just-in-time (JIT) provisioning, and SCIM-based user lifecycle management are all supported natively.

For enterprises with multiple identity providers, ORBI's identity broker can federate across up to 8 IdPs simultaneously, allowing phased migrations without disrupting existing access.

What are the developer API rate limits for custom integration?

Dedicated enterprise instances support up to 10,000 REST requests per minute with zero throttling on local WebSocket hardware triggers. Burst capacity extends to 25,000 requests per minute for up to 30 seconds, with priority queuing for authenticated admin operations.

All API traffic is versioned, logged, and can be routed through your own API gateway for additional rate limiting or inspection.

Can the Campus Recruitment Module process non-standard resume formats?

Yes. The parsing engine processes PDF, DOCX, scanned images via OCR, and web portfolio links, extracting structured skill vectors automatically. Over 40 file formats and 12 languages are supported out of the box, including CJK, Arabic, and right-to-left scripts.

Does ORBI integrate with existing ATS or HRIS platforms?

ORBI provides first-party connectors for Workday, SAP SuccessFactors, BambooHR, Greenhouse, and Lever. For any other system, our REST API and webhook framework allow two-way synchronization with custom workflows in under a day of engineering time.

02

Deployment & hardware

Does ORBI require a constant internet connection?

No. ORBI is engineered as an edge-native device. All inference, storage, and routine operations run entirely on-device. Internet connectivity is only required for optional cloud sync, remote admin policy updates, and firmware upgrades — none of which are mandatory for day-to-day operation.

How is the hardware deployed in an air-gapped environment?

Enterprise deployments in air-gapped environments receive a signed offline firmware bundle and a USB-based provisioning kit. ORBI devices pair with an on-premise controller node that manages policies, updates, and telemetry entirely within the corporate network perimeter — with zero outbound traffic.

What is the typical rollout timeline for a 1,000-seat deployment?

Most enterprises complete a 1,000-seat rollout in 3–4 weeks: 1 week for procurement and staging, 1–2 weeks for network preparation and pilot group, and 1 week for full fleet provisioning and employee onboarding. Larger deployments follow a phased wave model with a dedicated Innovexa deployment engineer.

03

Compliance & security

What certifications does the ORBI platform hold?

ORBI is certified for SOC 2 Type II, ISO 27001, ISO 27701 (privacy), GDPR, and CCPA. Financial services customers can additionally receive deployment blueprints aligned with PCI-DSS and FFIEC guidance. Certificates are available on request through the enterprise trust portal.

Where does employee data physically live?

By default, all employee data is stored locally on-device with encrypted at-rest storage. If cloud sync is enabled, data is encrypted in transit with TLS 1.3 and at rest with AES-256, in the region the enterprise selects during onboarding. No data leaves the selected region under any circumstance.

How does ORBI handle right-to-erasure (RTBF) requests?

Admins can issue a cryptographic erasure command that destroys the on-device data encryption key, rendering all associated data irrecoverable within seconds. Cloud replicas are synchronously purged across all regional nodes within 24 hours, with an audit log delivered to compliance teams.

04

Procurement & SLA

What are the standard SLA terms for enterprise contracts?

Enterprise customers receive a 99.9% uptime SLA for cloud-connected features and a 99.99% replacement SLA for hardware failures (overnight shipping within supported regions). Premium support tiers add a 1-hour P1 response time and a dedicated technical account manager.

Can we purchase ORBI through our existing procurement channels?

Yes. ORBI is available through direct enterprise sales, major cloud marketplaces (AWS, Azure, GCP), and select resellers. We support purchase orders, multi-year prepayment, and enterprise invoicing — and we can accommodate custom procurement frameworks for regulated industries.

What does the hardware warranty cover?

The standard warranty covers all manufacturing defects and component failure for 36 months from deployment. Enterprise tiers can extend to 60 months, with optional accidental-damage coverage for high-touch environments such as shared desks and campus labs.

Is there a pilot or trial program available?

Yes. Qualified enterprise prospects can request a 30-day pilot with up to 25 units, including a deployment engineer, integration support, and a post-pilot ROI report. Contact our sales team with your expected deployment size to get started.

Talk to an Engineer

Still have questions?

Our enterprise solutions team is available for technical deep dives, architecture reviews, and procurement discussions.