DEV3 Quarko – Dynamic QR Code SaaS Laravel Script with Designer, Editable Destinations, Bulk Runs & Analytics

Quarko is a QR code platform that you run as a multi-tenant SaaS, built by DEV3 Technologies on Laravel 12 and Filament 4. Workspaces design codes for menus, packaging, posters and window cards, choose static or dynamic, and download print-ready files. A dynamic code points at a short address on your domain, so the destination can change after printing while every scan is counted. You sell plans, and every workspace is isolated from the others.

What it does

• Fourteen code types. Web address, contact card, Wi-Fi, plain text, email, SMS, phone, location, calendar event, menu PDF, app store chooser, social links, coupon and SEPA payment. Menu, coupon, social and app store codes open a landing page; the rest carry their content or redirect.
• A designer with a scan check. Live preview with colours, gradients, dot styles, eye styles, a logo and a frame with your own call to action. A scannability score covers contrast, quiet zone, print size, error correction and logo size. Quarko raises error correction for a big logo, refuses a design below the safe score and warns about inverted codes.
• Edit after print. Change where a printed code leads, schedule the next destination, pause, resume or archive, and keep every earlier destination in a history. Redirects are 302 with no caching, so a change takes effect at once.
• Print-ready exports. SVG and PNG with a resolution, plus a PDF with bleed and crop marks (TrimBox and BleedBox set) and an EPS, written by Quarko itself. Download links are signed and expire after 15 minutes.
• Bulk runs from a CSV. Download a template per type, upload, read the row-by-row validation report, confirm the valid rows and download a ZIP with one file per code and an index CSV. Runs resume after a worker restart and can be cancelled.
• Scan analytics. Scans and unique scanners, trends, top cities, countries, devices, referrers, a compare view for four codes, CSV download, and the Scan Clock: a flat weekday-by-hour chart in the workspace time zone.
• Branded domains. Each workspace can verify its own scan domain with a CNAME and a verification record, so printed codes carry its name.
• Landing pages that work on a phone. Menu viewer, contact card with Save contact, event card with Add to calendar, Wi-Fi card, coupon reveal and social links, including right-to-left pages in Arabic.
• Limits that count scans. Plans meter dynamic codes, monthly scans, bulk rows, branded domains and API calls. At the cap, codes keep working through a small grace allowance and the owner is emailed at 80 and 100 percent.
• Trust and safety. A public report form, a safe-link queue where a person confirms or blocks a destination with a reason, takedowns, a neutral page for paused or blocked codes and an audit log.
• SaaS layer. Plans, trials, billing page, invoices, team roles (owner, designer, viewer), an operator panel with usage per workspace and audited impersonation.
• API (plans with API access): scoped keys hashed at rest, rate limits with headers, one error envelope and an OpenAPI document.

Install and demo data

A web installer checks the server, writes the configuration, migrates and loads either demo data or an empty install, then creates the operator account. The demo has 24 fictional workspaces, about 1,300 codes, ten months of history and about 90,000 raw scans, including a café group, a hardware co-op with a 2,400-SKU bulk run, an events company and an estate agent. Every demo password is password. Node.js is not needed because compiled assets are included.

Good to know before you buy

• Drivers are simulated until you configure them. Subscription payments run on a simulated gateway (Stripe, Razorpay and PayPal are present), mail is written to the log until you set SMTP, and scan locations come from a fictional table until you add a GeoLite2 file.
• The safe-link check is guarded off by default. The built-in driver flags a list of test hosts only. To check real destinations you enable the Safe Browsing driver with your own key.
• You are the merchant of record. Quarko handles no money between a workspace and its scanners; your customers pay you, and tax, invoices and refunds are your responsibility.
• PNG uses GD; Imagick is optional. With GD the PNG is anti-aliased. Without GD a pure-PHP writer draws square modules only.
• EPS colour is approximate. CMYK values are converted from RGB; ask your printer for a proof if colour matters.
• The fully round "dots" style reads less reliably in some scanner libraries, such as jsQR, than in a phone camera. The scan check is a guide, not a guarantee: always scan a printed proof with two or three phones.
• Branded domains need your TLS and DNS. Quarko verifies the records but does not issue certificates.
• Web only. There are no mobile apps.
• Name: Quarko is a working name checked by a web search only, not a trademark clearance. Check it before launching under it.
• No hosted demo. The brands, people and places in the screenshots are fictional.

Quality checks

Quarko 1.0.0 passed the seven release gates of the DEV3 Laravel suite on the final code: static analysis (Larastan level 6), the Pest suite (395 tests), a front-end size budget, migrations and seeding on MySQL 8 and SQLite, a headless-browser pass over 135 pages and 59 happy paths with MySQL race checks (parallel creates at the dynamic limit, 200 parallel scans, scans across the cap, parallel bulk runs), exports decoded back with a QR reader, an installer test from the package and a secret scan.