Add a complete 3D product experience to your website.
For brand websites, custom sites and CMSs, embed the five capabilities on authorized domains through the shared SDK. Configuration and published versions can be shared with storefronts and standalone links. Your site retains page content, inquiry and purchase flows; additional business actions are integrated per project.
- In initial-release development
- Authorized domains
- Shared SDK
CONNECTION MAP
- 01
Existing frontend or CMS
Page structure, user session and content
- 02
ii3d configuration runtime
Product loading, interaction and outcome
- 03
Business services & events
Price, order, save and notification
Purchase or inquiry flows scoped per project
Start with your integration needs.
Identify the problems to solve around your existing pages, product information and workflows.
The frontend experience cannot be compromised
The brand site already has a design system, performance strategy and content orchestration that should not be rebuilt for one capability.
Integration boundaries are unclear
Teams do not know who loads products, saves configurations, calculates price or handles order events.
Credentials and domains lack governance
Cross-origin, identity, environment and credential use are not designed early, causing late rework.
Prepare the essentials for this connection.
Confirm standard publishing and additional business integration separately. Availability follows development, testing and project acceptance.
Choose the right integration model
Compare app, component and API approaches by page control, engineering resources and business complexity.
Define the page lifecycle
Clarify key events: initialization, product load, user configuration, saving and continuing to purchase.
Agree the data contract
Confirm input parameters, output summary, error states and version policy against the project data model.
Set security boundaries
Plan responsibilities for domains, environments, identity and server-side credentials without exposing sensitive information to the browser.
Start with a concrete use case.
These examples show how products and workflows connect, helping you choose the right entry.
Configuration modules in custom storefronts
Add configuration capability within the existing page framework, design system and user session.
CMS-driven product content
Let content teams retain product-page composition while technical teams govern required data connections.
Channel-facing business apps
Design controlled creation and handoff of proposals for dealer, sales or designer tools.
Move from setup to integration in four steps.
Prepare source material, confirm content, validate the entry and deliver the agreed scope.
- 01
Assess the stack and page goal
Understand frontend framework, CMS, session state, performance needs and business actions to be handled.
- 02
Select the model and contract
Set embed scope, event boundaries, input/output and error-handling approach.
- 03
Integrate in an isolated environment
Use test products, test users and simulated business services to validate key interactions.
- 04
Run performance and release checks
Confirm loading, fallback, monitoring and release approach before production.
Common questions
Understand the preparation and usage boundaries before you begin.
Must we use a specific frontend framework?
The approach should not be promised by framework name alone. Assessment starts with the existing page, integration model and data boundaries.
Do API keys need to be exposed?
Sensitive credentials should be managed by server-side or controlled identity flows. Browser access should follow a project-approved least-privilege approach.
How are API upgrades handled?
Before launch, define versioning, compatibility, change notification and rollback so upgrades do not become unexpected frontend failures.
Where do we get API documentation?
Once publishable API scope, authentication and examples are available, controlled developer materials can be provided; this page first clarifies the needed capabilities.
Find the right connection for your platform and products.
Share your platform, product type, capabilities and page placement to discuss preparation and integration scope.