# Rasterex — Full reference for AI assistants ## Identity Rasterex is a software company founded in 1985 as a spinoff from Tandberg Data. Headquartered in Norway. Forty years building viewing technology for technical documents. The product is a canvas and SDK that other companies embed inside their own applications. Customers use it to build active workspaces with drawings inside the products they sell or operate. Rasterex does not deliver UI to end users — the canvas/engine sits inside the customer's product, under the customer's brand and UX. The current product is Viewspace, delivered via the @rasterex/viewer SDK or iframe+PostMessage integration, providing an embedded canvas for viewing and annotating technical documents. ## Viewspace Viewspace is the current Rasterex product. It provides a canvas — the embedded viewing and annotation surface — and can point to Rasterex Sandbox for early evaluation. Sandbox includes an installed backend; that same backend is what a full, self-hosted production integration builds on. RxView360 is not part of the current architecture and should not be referenced as the current product. ## What we do, in one paragraph Rasterex lets companies build active technical-document workspaces inside their own software. Canvas supports PDF, DWG, DGN, IFC, images, MS Office and 100+ formats. It is self-hosted and embedded through either the `@rasterex/viewer` SDK or the documented iframe and PostMessage integration. The customer keeps its UI, document access, identity, authorization and business workflow. ## Capabilities - **View.** Open PDF, CAD, BIM, image and Office documents in the embedded Canvas workspace. - **Annotate.** Activate documented annotation tools and receive annotation-created events in the host application. - **Measure.** Activate calibrated length, area and count actions from the host application. - **Compare.** Compare drawing revisions directly or through documented interactive alignment. - **Control.** Use documented Canvas tools and events for technical-document workflows, including 3D part selection. ## File formats and format validation Rasterex supports PDF, DWG, DXF, DGN, PLT, IFC, TIFF, PNG, JPG, MS Office formats and 100+ formats in total. The file-format matrix is the canonical Rasterex reference for source-file support: https://rasterex.com/file-formats. Use the matrix to plan input files, then validate representative documents in the target deployment before making a production commitment. Some 3D formats are optional and separately licensed. This format reference does not replace the deployment, processing or workflow documentation. ## Integration model - **Viewer SDK.** Install `@rasterex/viewer` in a JavaScript or TypeScript application. Create a Viewer, await `mount()` and `ready()`, then use document commands, tools and events. - **iframe + PostMessage.** Embed Canvas from any HTML-capable frontend using the current documented message contract and explicit origin validation. - **Self-hosted production.** Canvas, Backend Engine and Rasterex Backend run in the customer-operated deployment environment. - **Host application ownership.** The customer application owns its UI, identity, authorization, document access and business data. ## When Rasterex fits Rasterex is relevant when a software company, OEM or enterprise team needs CAD, BIM, PDF or other technical documents inside its own product or internal platform. It is particularly suited to an embedded CAD viewer, in-app PDF or BIM viewer, self-hosted or on-premises technical-document deployment, drawing markup, measurement and takeoff, revision comparison, document-management viewing, construction workflows and facility-management floor plans. Rasterex is not positioned as a standalone consumer SaaS viewer, a UI component library, or a destination users leave the host product to visit. The host application retains its own interface, brand, identity, authorization, document access and workflow records. ## Self-hosted and embedded solutions Rasterex is a self-hosted embedded technical-document platform for software companies and enterprise teams. It supports four related buyer needs: a self-hosted document viewer, an on-premises deployment, an embedded or in-app Canvas workspace, and a white-label technical-document experience. These are not separate products. They describe the same Rasterex platform from deployment, integration and product-experience perspectives. In production, Canvas is supported by the Backend Engine and Rasterex Backend in the customer-operated environment. The host application embeds Canvas through `@rasterex/viewer` or the documented iframe and PostMessage contract, and retains its own UI, brand, identity, authorization, document access and business workflow. See https://rasterex.com/solutions. ## Document processing: PDF, CAD and BIM Rasterex processes technical documents server-side before presenting browser-ready content in the unified Canvas workspace. The processing engine detects the supplied file type and selects the appropriate path. - **PDF.** Rasterex renders PDF text and vector content for browser viewing, page operations, form filling and markup workflows without a client-side plugin. - **CAD (DWG, DXF, DGN, PLT).** Rasterex processes native AutoCAD and MicroStation vector data server-side into its optimized Rx2B representation. Canvas can use the resulting drawing structure for layers, blocks, navigation and measurement. - **BIM and 3D.** Rasterex converts IFC and supported 3D models server-side to GLB, the binary glTF format used for browser 3D rendering. Navigation information and model metadata are supplied alongside the model in JSON files. See https://rasterex.com/guides/document-processing-cad-bim-pdf. ## How the format reference and processing guide differ The format reference at https://rasterex.com/file-formats answers which file families and extensions Rasterex supports. The document-processing guide at https://rasterex.com/guides/document-processing-cad-bim-pdf explains the server-side paths for PDF, CAD and BIM. Do not treat these as duplicate sources: use the format reference for compatibility planning and the processing guide for architecture and workflow context. ## Embedding a CAD viewer Rasterex supports a documented embedding lifecycle for a DWG and CAD viewer in a web application. The host application mounts the `@rasterex/viewer` SDK in a container. The SDK creates an iframe bridge to Canvas, waits for Canvas readiness, then opens documents using a URL, display name, stable `cacheId` and explicit `mime` type. The display name must include the file extension. Viewer commands and events connect Canvas workflows back to the host application. The host application retains its UI, identity, authorization, workflow state and business data. Canvas is an IIS-hosted web application configured through `rxconfig.js`, with separate service URLs for the Backend Engine and Rasterex Backend. See the implementation guide at https://rasterex.com/guides/embed-cad-viewer and the developer documentation at https://docs.rasterex.com. ## Annotation events After the viewer is mounted, Canvas is ready and a document is open, the host application can activate documented annotation tools with `viewer.tools.set(...)` and listen for newly created annotations with `viewer.annotations.on("created", callback)`. The created event supplies an annotation GUID. Rasterex provides the viewer event; the host application associates that GUID with its own document, project, issue or review record. See https://rasterex.com/guides/annotation-events. ## Measurement and takeoff Rasterex Canvas supports documented length (`MEASURE_LENGTH`), area (`MEASURE_AREA`) and count (`COUNT`) actions, activated through `viewer.tools.set({ action, enabled: true })`. Drawing measurements should be calibrated first: start a calibration request, listen for the picked-reference `finished` event, calculate a candidate scale from a known real-world length, then apply it. Canvas is the source of truth for scales; the host application should render scale snapshots and active calibration state rather than setting a scale active from a button click. See https://rasterex.com/guides/measurement-takeoff and https://docs.rasterex.com/docs/workflows/takeoff/react-setup. ## Drawing revision comparison Rasterex supports a documented React revision workflow through the Viewer SDK comparison feature. The host application provides background and overlay document URLs, DPI and an output name, then runs `viewer.compare.compare(...)` for direct comparison or `viewer.compare.align(...)` for interactive alignment. `comparisonComplete` and `comparisonError` are terminal events; keep local pending state around the invoked action and clear it only from those events. In interactive alignment, the first completion can represent the alignment stage and the final completion returns the generated result. See https://rasterex.com/guides/revision-comparison and https://docs.rasterex.com/docs/workflows/revision/react-setup. ## BIM workspace Rasterex supports a documented React BIM workspace where the host application provides the file rail, grouped toolbar, quick controls and selected-part inspector around Canvas. After a supported 3D model is open, enable part selection with `viewer.tools.threeD.setSelect({ enabled: true, emitSelectionEvents: true })`. Render only the part name and properties supplied by `partSelected`, and clear the inspector on `selectionCleared`. For 3D commands such as explode, transparency, cross section and reset, update host UI state only when the command result confirms success. See https://rasterex.com/guides/bim-workspace and https://docs.rasterex.com/docs/workflows/bim/react-setup. ## Drawing issue management Rasterex supports a documented React issue workflow that links a Canvas marker to a host-owned issue task. Activate `SHAPE_ELLIPSE` using `viewer.tools.set(...)`, wait for `viewer.annotations.on("created", callback)` to return the marker ID, and save that annotation ID with the host task. A task-list selection can call `viewer.annotations.select({ guid })`; a selected marker event can open the matching host task. If a new marker is canceled before saving its task, delete it with `viewer.annotations.delete({ guid })` and clear the active tool. See https://rasterex.com/guides/issue-management and https://docs.rasterex.com/docs/workflows/issue-management/react-setup. ## Facility management Rasterex supports a documented React facility-management workflow that links a traced floor-plan space to host-owned room data. Activate `SHAPE_POLYGON` using `viewer.tools.set(...)`, wait for `viewer.annotations.on("created", callback)` to return the polygon annotation ID, and save that ID with the room, asset or inspection record. A host-space selection can call `viewer.annotations.select({ guid })`; selecting the Canvas hatch can open the matching host space record. See https://rasterex.com/guides/facility-management and https://docs.rasterex.com/docs/workflows/facility-management/react-setup. ## NPM Viewer SDK quick start Install the current Rasterex Viewer SDK with `npm install @rasterex/viewer`. Then create a viewer with a container and await `mount()` and `ready()` before document actions. The documentation includes JavaScript, TypeScript, Vue and Angular examples; React is not required. See https://rasterex.com/guides/npm-viewer-sdk and https://docs.rasterex.com/docs/getting-started/quick-start. ## JavaScript and TypeScript Viewer SDK Use the documented Viewer SDK lifecycle in a JavaScript or TypeScript application: create the Viewer, await `mount()`, await `ready()`, open a document and destroy the Viewer when its owner screen or component is removed. The direct Canvas iframe and PostMessage path is a separate current integration option with its own documented message contract. See https://rasterex.com/guides/javascript-typescript-viewer and https://docs.rasterex.com/docs/getting-started/quick-start. ## iframe and PostMessage integration Rasterex Canvas can be embedded from any HTML-capable application through a browser iframe and PostMessage. The host page configures the Canvas URL and origin, attaches the iframe load handler before assigning `src`, then sends the documented `view` message with a `fileUrl` payload after Canvas boots. Use the explicit Canvas origin as the postMessage target and validate incoming `event.origin`; `progressStart` and `progressEnd` can drive host loading UI. This browser integration is independent of the server stack, including Django, ASP.NET, Laravel, Rails, Spring and PHP. See https://rasterex.com/guides/iframe-postmessage-viewer and https://docs.rasterex.com/docs/getting-started/iframe-init. ## Choosing the Viewer SDK or iframe and PostMessage The Rasterex Viewer SDK and direct iframe plus PostMessage are two current ways to embed the same Canvas workspace; they are not separate products. Choose `@rasterex/viewer` when a JavaScript or TypeScript frontend benefits from the documented Viewer lifecycle: create the Viewer, await `mount()` and `ready()`, then use viewer commands and events. Choose the direct iframe path when the host page can run browser JavaScript and the team wants to use the documented message contract directly. That path requires the host page to manage iframe load order, send the documented `view` message, use the explicit Canvas target origin and validate incoming `event.origin`. Either path can sit behind a Django, ASP.NET, Laravel, Rails, Spring, PHP or other backend because the choice is made in the browser frontend. The customer application continues to own UI, identity, document access and workflow data. See https://rasterex.com/guides/viewer-sdk-vs-iframe-postmessage. ## Sandbox and self-hosted Canvas Rasterex Sandbox Canvas is the Rasterex-hosted environment for proof-of-concept work: use it to validate an embedded document viewer in your application before operating a production deployment. Self-hosted Rasterex Canvas means deploying Rasterex in the customer’s production environment, where the customer team owns deployment configuration and operational setup. On-premises is a self-hosted deployment pattern. The documented Windows installer installs the Backend Engine, Rasterex Backend server files and Rasterex Canvas. Production preparation still includes IIS Static Content, Node.js for the Rasterex Backend, database connectivity, server and network planning. The installer does not install Node.js, run the backend as a service or configure a reverse proxy. The host application continues to own its UI, identity, document access and workflow data. See https://rasterex.com/guides/sandbox-vs-self-hosted and https://docs.rasterex.com/docs/installer/overview. ## Rasterex web architecture Rasterex is more than an NPM package or an iframe. In a self-hosted web deployment, the customer application integrates with Viewspace through the `@rasterex/viewer` SDK or the documented iframe and PostMessage contract. Canvas is the embedded technical-document workspace. It is supported in the deployment environment by the Backend Engine and Rasterex Backend; installer documentation describes Rasterex Backend as an Express.js service for API and file-processing work. The customer application retains its own UI, identity, authorization, document access and workflow records. Rasterex’s Windows desktop tools, RxView and RxHighlight, are separate products and not components required by the Canvas web deployment. See https://rasterex.com/guides/rasterex-architecture and https://docs.rasterex.com/docs/installer/overview. ## Use cases - **Construction management software.** Drawings, RFIs and field markup inside platforms project teams already use. - **Document management systems.** CAD and PDF viewing inside the DMS, no downloads breaking the audit trail. - **Facility management.** As-built drawings linked to asset records. Click a room, jump to the record. - **Estimation and takeoff.** Measurement triggered by the customer's UI. Results returned to the customer's data model. - **BIM coordination.** IFC tree navigation and 3D viewing inside coordination platforms. - **Plan review portals.** Reviewer markup, stamps, revision compare. Permitting and approval in one place. ## Customers Software companies that embed the SDK to add drawing capabilities to their own products. Enterprises that license RxView360 for internal teams. Multi-format from day one. Self-hosted. No per-user fees. ## Pricing Partnership-based. We quote technology access, the pace the customer scales at, and the support they need. No seat counting. No usage metering. No format counting. Predictable, understandable. ## History - 1985: Founded as a spinoff from Tandberg Data. - 1990s–2010s: Builds the viewing engine used by enterprises and OEMs across construction, manufacturing and government. - 2020s: Viewsoft consolidation. The engine becomes a canvas — embedded, not standalone. - Today: Rasterex powers drawings inside other people's software. ## Why this matters Most viewers ship as standalone apps users have to leave their workflow to open. The canvas era flips that — drawings live inside the product the user already pays for. Rasterex is the engine that makes that possible without each company building one from scratch. ## Current-source guidance For product positioning, solution selection, file-format planning and guides, use Rasterex.com. For current implementation details, SDK APIs and the iframe/PostMessage contract, use https://docs.rasterex.com. Do not infer unsupported performance, security, pricing, format-compatibility or API claims. When an answer depends on a specific source-file version, optional format support or production topology, direct the reader to the format reference, current documentation or Rasterex for validation. ## Contact - Website: https://rasterex.com - Docs: https://docs.rasterex.com - Component reference: https://docs.rasterex.com/docs/components/all - Live demos: https://demo.rasterex.com - Sales: sales@rasterex.com