One feed at full size, the rest of the line beneath
Drop the component into a Perspective view and size it however the screen needs — one stream front and centre for the cell that matters, the rest of the line along the bottom.
A Perspective component that streams your RTSP cameras straight into Ignition. Drop it on a view, pick your cameras, and your team gets a multi-camera grid they can click to expand — for security, custom views, or live floor context next to alarms and OEE. Free up to 3 feeds. Part of our Ignition module lineup.
CAM 02 · LINE 3 · ASSEMBLYLIVE
Micro-stop · Cell M2
CAM 01LIVE
Infeed
CAM 03LIVE
Packout
CAM 04LIVE
Buffer
CAM 05LIVE
QCOne Perspective view, no extra software — RTSP streams rendered natively, with no NVR client and no browser plugin.
Capabilities
RTSP cameras
Works with any IP camera that provides an RTSP stream, in H.264 or H.265 — repackaged, never re-encoded.
Perspective component
Drop it on a view, pick your cameras, done. Click any tile to expand.
Credentials stay server-side
Cameras are configured on the gateway and referenced by name, so credentials never reach the browser.
Built for many feeds
Roughly 100–200 feeds per gateway in our load testing. Real capacity depends on your cameras and hardware.
Automatic reconnect
Offline cameras reconnect on their own — no blank tiles to babysit.
One
.modl, no extrasA signed module with everything built in. Nothing else to stand up, backed directly by Parsley Automation.
Use cases
A few of the ways teams put RTSP for Ignition to work inside Perspective:
Security & CCTV viewing
Bring security cameras into Perspective so guards and managers watch entrances, yards and sensitive areas — no separate VMS client to log into.
Spin up custom views
Build a focused camera view for any person or role in minutes — a shift lead's line, a manager's whole plant, a contractor's single zone.
Alarm-driven camera pop-ups
Tie a feed to an alarm: when it trips, the relevant camera comes up on screen so the team sees what's happening on the floor, fast.
Cameras beside OEE & process data
Drop live feeds next to your tags and OEE so supervisors see the jam and the number move together — context, not guesswork.
Where your camera passwords live
A camera URL usually carries the credentials for that camera. Where those end up is a design decision, and it is worth knowing which one you are buying into.
01
Never sent to a browser
Perspective views reference a camera by name. The gateway resolves that name to the real URL and connects to the camera itself, so no camera address or password is ever delivered to a session, a browser, or anything a viewer can read.
02
Encrypted on disk
The password inside each camera URL is encrypted where the gateway stores it, not left in plain text. A gateway backup, a support bundle or a copied config file does not hand your camera passwords to whoever opens it.
03
Masked on the config page
Passwords show as *** to anyone with Config access, and saving a camera back keeps the stored one. People can manage cameras without ever being shown the credentials — including in a screenshot or a screen share.
04
Cameras stay off the client network
Video reaches the browser through the gateway, over its own port and its own TLS. Viewers never connect to a camera directly, so cameras do not need to be reachable from the machines watching them.
Camera credentials are configured once on the gateway and stay there. The alternative pattern — holding the camera URL in the view itself — puts the password wherever that view travels: the Designer, a project export, a backup, a screenshot of someone’s screen. No software can promise a secure network, and ours does not; what it can do is avoid handing the password to people and places that never needed it.
How licensing works
Buying is simple and the module runs on your own gateway:
1
Free
install the .modl, add cameras under Connections → RTSP Cameras (bulk paste works) — done, capped at 3 feeds.
2
Paid
check out and send us the Ignition license key from your gateway (Config → Licensing shows it). We issue the module license against that key, and you activate it the same way you activate Ignition itself — Config → Licensing → Update License. The feed cap lifts within seconds, with no gateway restart.
3
Activation
online activation is a single click, and offline activation works too — fine for air-gapped plant networks.
4
Per gateway
one license covers one Ignition gateway, perpetual. Running the module on a second gateway needs a second license.
Pricing
| Free$0 | Pro$3,500 |
|---|---|
| up to 3 feeds · forever | /gateway · perpetual |
| Up to 3 camera feeds | Unlimited camera feeds |
| RTSP streams in Perspective | One Ignition gateway |
| No license key required | Everything in Free |
| Unlimited on Ignition Maker Edition | — |
| Buy now — $3,500 |
For monitoring and situational awareness only — roughly 2–6 seconds of latency on HLS, about a second on WebRTC. Not a safety, security, alarm-of-record or real-time control system; keep independent monitoring, recording and alarms. Paid tiers are per-gateway and perpetual, with optional version upgrades at 20% a year. Card or US bank transfer, and your license is issued within one business day of receiving your gateway’s Ignition license key. Sales are final — the Free tier is there to check compatibility first. Need a PO? Request an invoice. Terms of Sale.
Frequently asked questions
Does it work on Ignition Maker Edition?
Yes, and Maker Edition gets unlimited camera feeds at no cost — the 3-feed limit does not apply. Nothing to buy and no license to activate; the module detects Maker on its own. Note that Inductive Automation license Maker Edition for non-commercial use only, so this covers home labs and personal projects rather than a plant.
How is it licensed?
Per Ignition gateway, perpetual — buy once, no recurring fee. “Perpetual” refers to your license for the version you bought; it is not a guarantee of compatibility with future Ignition versions. Licensed as-is — verify on the Free tier. Optional version upgrades at 20%/yr.
What's the video latency?
Two delivery modes. HLS is the default, typically 2–6 seconds behind live. WebRTC drops that to under a second.
Does it record video?
No. RTSP for Ignition displays live streams only — it does not record, store, or retain footage. Point it at your cameras for live viewing.
Can I start free and upgrade later?
Yes. Activate the license on the gateway at any time and the feed cap lifts immediately — no reinstall.
Are my cameras exposed to clients?
By design, cameras are configured server-side and referenced by name, so camera credentials aren't sent to Perspective clients and feeds proxy through the gateway web port you already expose. Your deployment's security also depends on how you configure and secure your gateway and network.
What cameras work?
RTSP — generic IP cameras, referenced by name from the gateway. Both H.264 and H.265 (HEVC) stream, repackaged rather than re-encoded, so image quality and gateway CPU are unchanged. H.265 playback depends on the viewer’s browser and hardware — current Chrome, Edge and Firefox on Windows 11 all play it, older machines without a hardware HEVC decoder may not, and a tile that cannot decode a camera says so rather than looking offline. If you don’t control your viewers, H.264 plays everywhere.
How many cameras can it handle?
In our internal load testing, a single gateway handled roughly 100–200 concurrent feeds at low CPU, with a dozen-plus tiles per screen. Real capacity varies with resolution, codec, bitrate and hardware, so your results may differ — verify on the Free tier.
Which Ignition versions?
Ignition 8.1 and 8.3+, as two separate builds â pick the one that matches your gateway, since neither installs on the other. RTSP for Ignition is distributed as a signed module, so it installs on standard production gateways without developer mode. Signing and compatibility are controlled by Inductive Automation and may change between versions — verify on the Free tier first.
Need something this does not do? We build Ignition systems for a living, so if you want the module extended, wired into something you already run, or a camera workflow built around it, tell us what you are trying to do.
Get in touch