Rasterex architecture: more than an NPM package or an iframe.
Rasterex is a self-hosted technical-document system. Your application embeds RxView360 Canvas, while the Backend Engine and Rasterex Backend support the document workspace in the deployment environment.
The SDK connects your product to a complete technical-document workspace.
The browser integration is intentionally simple: mount Canvas through the Viewer SDK or an iframe, open a document, then exchange commands and events. Behind that integration, a self-hosted deployment includes Canvas, the Backend Engine and the Rasterex Backend. Your product remains the system of record for users, permissions, documents and workflow data.
Four layers, with a clear responsibility boundary.
Customer application
The product your users know. It owns navigation, UI, identity, authorization, document access, business records and workflow decisions.
Integration layer
Use @rasterex/viewer to mount the Canvas bridge and work with its lifecycle, commands and events, or use the documented iframe and PostMessage integration.
RxView360 Canvas
The multiformat technical-document workspace embedded in the host product. It handles the on-screen viewing and interaction experience.
Supporting services
The Backend Engine and Rasterex Backend support Canvas in the deployed environment. Rasterex Backend is the documented Express.js service for API and file-processing work.
Name the backend technology correctly.
Backend Engine
The Backend Engine is installed as part of the documented Rasterex deployment and supports the technical-document system behind Canvas. It is not a JavaScript package that the host page imports.
Rasterex Backend
The installer documentation describes Rasterex Backend as an Express.js service for API and file-processing work. Production planning includes Node.js, database connectivity, service operation and networking around this service.
RxView360 Canvas
Canvas is the embedded technical-document workspace. Its deployment configuration connects it to the Backend Engine and Rasterex Backend; the host application then embeds Canvas in a product screen.
A web architecture built on a long technical-viewing history.
OEM and native-viewing roots
Rasterex began with graphics technology, evolved into native multi-format viewing and markup, and then made the technology embeddable in external enterprise products. That OEM model remains central to the Canvas approach.
Separate desktop products
RxView and RxHighlight are Rasterex Windows desktop tools for native viewing, markup and document work. They are separate from the web deployment; do not mistake a desktop capability for a required Canvas component.
Plan the full system, not just the browser snippet.
- Identify the host application screen and browser integration path: Viewer SDK or iframe and PostMessage.
- Confirm that Canvas can reach the configured Backend Engine and Rasterex Backend URLs.
- Plan the Node.js, IIS, database, service and network responsibilities for production.
- Test representative CAD, BIM, PDF or other technical documents through the complete environment.
- Keep host UI, identity, authorization, document access and workflow records in the customer application.
Rasterex architecture answers.
Is the Rasterex NPM package the whole product?
No. @rasterex/viewer is an integration layer. It mounts an iframe bridge to Canvas and exposes a browser-facing lifecycle, commands and events. Canvas runs with the supporting Backend Engine and Rasterex Backend services in the deployed environment.
What are the main components of a self-hosted Rasterex deployment?
The documented installer deploys the Backend Engine, Rasterex Backend server files and Rasterex Canvas. Canvas is the web workspace; the Rasterex Backend is the Express.js service for API and file-processing work; the customer application integrates with Canvas and owns its product workflow.
What is RxView360?
RxView360 is Rasterex’s multiformat web viewer. In the modern embedded model, Canvas is the technical-document workspace that the customer application places inside its own product.
Where do the customer application and Rasterex responsibilities meet?
Rasterex supplies the technical-document workspace and its supporting services. The customer application supplies the UI around it, identity, authorization, document access, business records and workflow decisions.
Are RxView and RxHighlight part of the web deployment?
No. RxView and RxHighlight are separate Rasterex Windows desktop tools. They demonstrate Rasterex’s native viewing and markup heritage, but they are not components of the Canvas web deployment described here.