BRINGING THINGS INTO FOCUS
+RAZANT STUDIO / Application scope to be evaluated
See it. Set it. Make sense of it.
The camera sees an image. You need an answer. Studio is the shared workspace for connecting the two, right in your browser.
CAMERA VIEW / FRAME 0001
REGION 01 Drag image or use sliders
SYNTHETIC DATA · NO CAMERA CONNECTEDLOCAL DEMO / NO DATA UPLOADED
Interactive frontend concept. Images, device status, decoding, and inspection results are synthetic. No hardware is connected and no image processing model runs here. Change the expected value, move the ROI, or select a non-matching sample to create a failed inspection.
+01 / RAZANT
The image is only the beginning.
A clear workflow that keeps acquisition, inspection tools, and acceptance rules visible together.
Start with a clear image.
Live preview, exposure controls, and regions of interest put image acquisition at the center of the workflow.
Build a readable recipe.
Compose acquisition, OCR, code decoding, counting, presence detection, classification, and explicit validation steps.
Make the rule visible.
Define what acceptable means. Inspect the relevant region, compare the result, and see the reason behind a pass or fail.
Look back at the evidence.
Use image history and inspection results to investigate exceptions and tune recipes. Specify retention and storage capacity for the installation.
Keep the work local.
A local-first runtime is the intended default. Configuration happens in the browser; inspection processing belongs near the camera.
Connect the next step.
Define result messages and interfaces around the receiving machine or production system. Agree the data contract as part of integration.
+ONE PLATFORM. MANY RECIPES.
Your process
sets the rules.
Save a setup for each part. Make the inspection understandable for the next person. Build a path from camera settings to a result that your process can actually use.
Application assessment defines the recipe, camera interface, user access and deployment requirements as one coherent system.
+Practical questions
A little more clarity.
Do I need a cloud account?
Studio’s intended configuration and inspection model is local-first. Final authentication, updates, and licensing are still being defined; no mandatory cloud dependency is claimed.
Is the demo the actual software?
No. It is a frontend demonstration of the interaction model. It uses synthetic sample values and deterministic rules, not real OCR, barcode decoding, classification, or camera input.
Will it work with non-RAZANT cameras?
Camera compatibility depends on the capture interface and driver. Share the exact camera model for an integration assessment.
What does Studio cost?
Packaging and licensing are not defined yet. We are collecting feedback from manufacturers and integrators before setting a commercial model.
+WORKFLOW & INTEGRATION
Live previewEditable ROIInspection recipesOCR and codesRule-based decisionsCapture history
| Runtime | Local-first Linux vision runtime architecture |
|---|---|
| Configuration | Browser-based UI |
| Integration | Ethernet / API integration scoped to the application |
+OPEN FOR APPLICATION EVALUATION
Better tools start with better questions.
Tell us how you configure, troubleshoot, and hand over inspections. Help us make Studio useful for the people on the line.
Discuss your application