RFID readers that arrive ready to work.
We ship Impinj R700 readers already configured for your account. Plug one in and your reads land in the cloud — nothing to install, nothing to run, and nothing for your team to build.
- Reader
- Impinj R700
- Arrives
- Configured for you
- Setup
- Plug it in
- Platform
- Fully managed
Read zones
- Receiving dock R700-01 412 tags/s
- Sort floor R700-02 288 tags/s
- Line 2 exit R700-03 907 tags/s
- Packout R700-04 164 tags/s
- Dispatch dock R700-05 0 idle
Recent reads
1,771 tags/s total| EPC | Zone | Dir |
|---|---|---|
| 3034F4D2 8A1B0C77 | Line 2 | in |
| 3034F4D2 8A1B0C31 | Line 2 | in |
| 3034F4D2 91C4A208 | Receiving | in |
| 3034F4D2 6B77E014 | Packout | out |
| 3034F4D2 91C4A19F | Receiving | in |
Representative interface. The figures above are illustrative, not a customer deployment.
What you get, once the reader is on.
We would rather be measured than believed. This is what changes the day a reader starts reporting.
- One place for every read
- Every reader, on every site, reporting into one account under one view. Adding the next read point is a reader arriving in a box, not another integration project.
- Nothing for you to run
- No servers to stand up, nothing to patch, nothing to back up, and no database for someone on your team to inherit. The platform is hosted and kept current by us.
- It lands where you already look
- The operator console shows what is where and what moved. The same data feeds into the WMS, ERP, or MES your business already runs on, so nobody has to learn a new place to check.
Four steps, and you do one of them.
Most RFID projects stall in the software, because nobody owns the part between a reader and the systems the business runs on. We own that part, and we would rather hand you a reader that already works than a project.
- 1
Tell us what you need
How many read points you expect, across how many sites, and what you want to track. Short conversation — we are not going to send a consultant.
- 2
Readers arrive configured
We ship Impinj R700 readers already set up and bound to your account. They need procuring and configuring first, so this takes a little lead time — and it means nothing lands on your team.
- 3
Plug them in
Give a reader power and a network connection and it comes online by itself. There is no commissioning step, no software to install, and nothing to configure on site.
- 4
Use it
Reads appear in the operator console as they happen, and flow out to the systems you already run. Already own R700s? You can set them up yourself instead — we will walk you through it.
Plug it in. That is the install.
A reader arrives configured for your account. It powers on, it connects, and the reads start landing. There is no software for your team to write, nothing extra to add to the cabinet, and no project plan.
Scroll the diagram, or read it as a list below.
-
Your readers
Impinj R700s, shipped configured by us or set up by you. Antennas, tags, and mounting stay with you or your integrator.
-
TitanRFID
Everything between the reader and your systems, run as a managed service. Nothing for you to host, patch, or back up.
-
Your systems
The operator console, plus a feed into the WMS, ERP, or MES your business already runs on.
You may not need another system.
If you are tracking this on spreadsheets today, the console is the system. It holds your own data against your own tags, so there is nothing else to buy, nothing to keep in sync, and no second place to look.
It is not order fulfilment, finance, or production scheduling — if you run a WMS or an ERP, Titan feeds it rather than replaces it. But for what you have, where it is, and what moved when, this is the record.
Tag Data
The one that mattersA spreadsheet whose rows are your tags and whose columns are whatever you want to track — SKU, price, colour, bin. No schema to design and no types to declare. Import a CSV that has an EPC column and every other column becomes a field. Every row keeps its history, so a tag reused for something else still has an auditable trail.
- Inventory
- What is present in each zone right now, how long it has been there, and what is there that you were not expecting.
- Assets
- Asset tag number, category, who has it, how long it has sat, and when it was last seen.
- Dock Doors
- Portal transits with a direction and a confidence, so an item leaving is a different event from an item arriving.
- Live
- Reads as they happen, with antenna, zone, and signal strength — the screen you watch while you are tuning.
- Alerts
- Raised by kind and severity, with an opened time, so exceptions come to you instead of being hunted for.
- Dashboard
- Reads per hour, tags by zone, recent activity. The view that answers "is it working" in one glance.
- Zones, Readers, Settings
- Your layout, your hardware, and your people — users and roles, API keys for integrations, and your plan.
Titan never writes to your tags. It attaches your data to the tags you already have, so trialling it cannot damage stock you have already encoded.
Managed cloud, nothing for you to run.
Hosted and kept current by us. Your team never sees a server, and readers arrive already configured for your account.
Titan Cloud
Managed by us
The operator console, your tag data, alerting, and reader health — all hosted and kept current by us. Nothing lands on your team.
- No infrastructure on your side
- Updates roll out with minimal downtime
- Reader health watched for you
- Readers ship configured and bound to your account
Measured, not estimated
- 5,000
- reads per second sustained with no loss — roughly three to five readers running flat out.
- 10,000
- reads per second at about 0.1% loss. We would rather state that than hide it.
Both figures were measured on a laptop running everything at once — the least favourable setup Titan will ever see. Treat them as a floor. A real server should do better, but we have not measured that, so we are not claiming it.
Where our job starts, and where it stops.
We handle everything from the reader onward. The physical work on your floor stays with you or whoever you already trust to do it. Knowing that before you talk to us is worth more than a longer list of services.
What we do
- Readers shipped already configured and bound to your account
- The managed platform: operator console, history, reporting, and alerting
- Setup guidance if you would rather configure readers you already own
- Reader health monitoring, so a reader that stops reporting raises an alert
- A feed into the WMS, ERP, or MES your business already runs on, if you run one
- Managed cloud hosting — none of it lands on your team
- Updates and upkeep handled by us
What we don't
- Site surveys, RF sweeps, and read-zone design Not us
- Installation, cabling, mounting, and antenna placement Not us
- Tag selection, supply, and commissioning Not us
Different question, and not on this list: handheld readers and deeper reporting are in development — ask where either stands. And if you already run a WMS or an ERP, Titan feeds it rather than replacing it.
Common questions
What people ask when they are deciding whether this is the right path for their operation.
- Is it Impinj R700 only, or will other readers work?
- The current version supports Impinj R700 readers. These are RAIN RFID fixed readers that handle the full UHF RFID band and deliver excellent read performance in industrial settings.
- Is there an on-premise version?
- No. Titan Cloud is a managed cloud platform. The infrastructure runs on our side, which means no servers to stand up, nothing to patch, and no database for your team to inherit.
- How long does installation take?
- Once a reader arrives, installation is power and network. There is no commissioning step and nothing to configure on site — the reader comes online by itself. The lead time is in procuring and configuring the readers before they ship.
- Can the readers write to tags, or just read?
- The R700 can write to tags. If your use case needs tag encoding or updates in the field, that capability is there.
- Can I bring my own R700 readers instead of ordering through you?
- Yes. If you already own R700 readers, you can set them up yourself to work with Titan Cloud. We will walk you through the binding process.
- Where does the data go after it leaves the reader?
- Reads appear in the operator console in real time. The same data feeds into your WMS, ERP, or MES through standard integration points, so your business systems stay current without anyone checking a separate portal.
- How many reads per second can the platform handle?
- The platform sustains 5,000 reads per second with no loss — roughly three to five R700 readers running flat out. At 10,000 reads per second, loss is about 0.1%. These figures were measured on a laptop, so treat them as a floor.
- What kind of support response do you provide?
- Email support at [email protected]. Because readers arrive configured and the platform is managed by us, most questions are answered before they come up. When something does need attention, we own the whole path from reader to console.
Tell us what you want to track.
The conversation is short: what you want to track, roughly how many read points, and where the reads should end up. Then readers arrive configured and you plug them in. We do not survey your site or install anything.
No deck, no obligation. We reply within one business day.