Where CardStudio works fine — and where it doesn't
Zebra CardStudio Professional is a solid desktop tool for a specific scenario: one workstation, one printer, one user. A receptionist designs and prints cards from one PC, with a USB cable to the printer next to it. For a dental practice, one hotel or a small office that's fine.
As soon as an organisation grows, the model breaks:
- Multi-site means installing, maintaining and updating CardStudio at every location — per Windows workstation.
- Non-Windows environments (Linux datacenters, macOS receptionists) drop out.
- Workflow integration (HR onboarding, PMS connection, visitor management) is impossible without an API.
- Audit trails for compliance (NEN 7510, ISO 27001) are missing in a form SIEM can read.
- Service staff have to walk to every workstation per location to change anything.
At that point CardStudio Professional is no longer the right tool. Not because the software is bad — but because it was intentionally not designed for server-side, multi-site or API-driven workflows.
What ConoCard does differently
ConoCard tackles the same problem at the architecture level: instead of a desktop tool on every workstation, there is one server-side service that drives the ZC350 over IP. Workstations (or HR systems, or PMS, or mobile apps) make an HTTP call. Done.
- No per-workstation driver installs — one Rust binary on one server.
- Cross-platform — Linux and Windows verified, 87 tests green on both.
- REST API as the integration surface — anything that speaks HTTP can request an issuance.
- Bearer-token authentication — secure by default, no open networks required.
- Append-only JSON-Lines audit log — ingestible directly by a SIEM.
- Webhook output — feed any other access-control or PMS system alongside 2N.
Point by point: CardStudio vs ConoCard
| Aspect | Zebra CardStudio Professional | ConoCard |
|---|---|---|
| Architecture | Desktop tool per workstation | Server-side REST service |
| Operating system | Windows only | Linux + Windows |
| Printer control | USB tether or Silex SX over IP (with Windows driver) | Directly over IP, driver-free |
| API | None | REST API |
| Multi-printer per host | Limited | Source-IP demux |
| Authentication | OS user per workstation | Bearer token (constant-time compare) |
| Audit trail (SIEM-ready) | None standardised | Append-only JSON-Lines |
| UID readback in the same session | Separate process | Inline in the response |
| 2N Access Commander integration | Manual, after printing | End-to-end in one REST call |
| Workflow integration (HR, PMS, ticketing) | Not possible | Native via REST + webhook |
| Multi-site management | Install per location | One instance serves multiple printers |
| Licence per workstation | Yes | One service licence |
| Updates | Per workstation | Centrally, one binary |
Migration scenario: from CardStudio to ConoCard
An organisation with a CardStudio installation can switch in three steps, without replacing hardware:
Step 1: decouple the design
The visual card design is exported once as a template (vector or bitmap). This design is loaded into ConoCard as a single source of truth for all locations. Design work itself — typography, colours, photo positioning — can still happen in a graphics program; CardStudio is no longer needed for it.
Step 2: roll out the ConoCard server
One Linux VM or Windows server (or a Raspberry Pi for small deployments) gets the ConoCard binary. The Zebra ZC350 is placed on the network (all ZC350s with the network option have the Silex chip on board). No more drivers are installed on workstations. The printer IP is configured in the ConoCard service.
Step 3: hook up workflows
For each use case, the relevant workflow is connected to ConoCard via REST. HR systems, visitor management, a PMS or a mobile app make HTTP calls. The reception desk gets an optional simple web page or mobile button. The CardStudio installations on the workstations can be uninstalled or kept as a fallback.
Tip for compliance environments: the ConoCard audit log lands in JSON-Lines from day one and is directly ingestible by Splunk, ELK or Microsoft Sentinel. That gives the compliance officer an audit trail CardStudio doesn't produce by itself.
TCO: total cost of ownership
The visible licence cost of CardStudio Professional is usually not the real cost item. In an operational organisation, you mostly pay for:
- Windows licences per workstation where cards are printed
- IT time for driver installs, updates and troubleshooting per workstation
- Per-workstation hardware (PC or laptop) that would otherwise not be needed
- Operational time spent manually copying UIDs into access-control systems
- Compliance overhead to reconstruct audit trails from disparate sources
The ConoCard model removes the first three items, automates the fourth, and delivers the fifth for free as a side effect.
Frequently asked questions
Does ConoCard fully replace CardStudio?
For server-side card-issuance scenarios: yes. ConoCard replaces the Zebra driver stack and the tool used to send print jobs. For design work (creating card designs with logo, layout, fonts), a tool like CardStudio or a design program remains useful — the design is then imported as a template into ConoCard.
Do I still need Windows licences?
No longer per workstation. ConoCard runs on one Linux VM, Windows server or Raspberry Pi for the whole organisation. CardStudio Professional requires a Windows licence per workstation where you print cards.
Can my receptionists still design cards graphically?
Yes — but the design is created centrally, not per receptionist. Templates are produced once and then used by everyone through the REST API. That's intentional: one consistent design across all locations.
Does it work with our existing Zebra ZC350 fleet?
Yes, provided the printers have the standard network option (Silex SX-200 chip on board). No firmware upgrade needed, no hardware replacement.
What about support and SLA?
Conocido is an NL-based MSP. Support is available in Dutch and English, by phone and email. SLA options are agreed per concrete deal.