Phyre Development & Road Map

2026-08-16

Phyre started as a set of resources built for our own servers. The rule was simple: if it wasn't good enough to run in production on a full server, it wasn't good enough to sell. That rule hasn't changed, and it's why the catalogue grows slower than most stores.

This post is a straight answer to the question we get most in tickets, what are you working on, and when does it land? It also covers the two resources that just went live.

Just shipped

ph-licensecreator, License Creator (v1.1.0)

Build any licence your server needs and design what it actually looks like in hand. An in-world creator places the issuing points, and a React card editor handles the design side: layered elements, gradient backgrounds (linear or radial, multi-stop, with angle and opacity), background images and patterns, signatures with an optional rule beneath them, and text fields bound to real character data, pick "Date of Birth" and the layer names itself after the field.

Issuing, revocation and cancellation are wired through properly rather than cosmetically. Revoking a licence removes the framework licence and the inventory item and tells the holder; reactivating restores it. Officer-side cancellations deliberately leave the physical item with the citizen so it can be handed back at the Authorization Center. Admin settings broadcast to every connected player on save, so a change applies server-wide with no restart.

It binds itself to your stack, framework, inventory and clothing script are auto-detected, and System Info shows you exactly what it locked onto. Runs on Qbox, QBCore and ESX, across ox_inventory, ph-inventory, qs-inventory and qb-inventory.

ph-tablet, Tablet Shell (v1.5.0)

A tablet you hand to players, and a platform other scripts plug into. The shell is the product: home screen with pages, widgets and drag-to-reflow editing, a lock screen that surfaces notifications and unlocks straight into the app that sent them, an iPadOS-style Control Center, and Clock, Calendar, Map, Notes and Photos widgets.

The flashlight is a real one, toggle it and the tablet casts an actual light beam from your character's hand. The UI closes, the tablet stays out as a torch, and pressing the tablet key stows it. PhyreStore is a built-in app store where players uninstall and reinstall apps, saved per player, with Settings and the Store itself locked so nobody can strand themselves.

For developers, the point is the registration API: guest resources add their own apps with exports['ph-tablet']:registerApp(spec), plus sendAppEvent and notifyApp for live updates and notifications. Your scripts get a tablet UI without building a tablet. It also ships a usable tablet item auto-wired to ox_inventory, ph-inventory, qs-inventory, qb-inventory or ESX.

Where Phyre stands today

The catalogue is deliberately small. Plenty of the resources below run in production on our own servers and have for a while, that still isn't the bar for putting something on the store. Every resource we do list follows the same set of rules:

• Framework agnostic. ESX, QBCore and QBox supported from a single build, with a bridge layer you can extend for custom frameworks.
• Open configuration. Config files are readable, commented, and cover the things you actually want to change without touching core logic.
• Lifetime updates. Buy once. Every future version of that resource is yours, including reworks.
• Performance first. Idle resmon is published on every product page. If a script is heavier than we said, that's a bug and we treat it like one.
• Real support. Discord tickets answered seven days a week, not a FAQ page and a shrug.

Shipped and available

ph-licensecreator and ph-tablet, the two covered above, are what's live and purchasable today. Everything below is still in development. We'd rather publish a short shipped list that's honest than a long one that isn't.

In active development

These are real, working builds, several are well past a 1.0 internally, but "internally stable" isn't the same as "ready to sell". None of these are purchasable yet, and we won't list them until they are.

• ph-inventory: Server-authoritative grid inventory with a React NUI, built to replace the framework default rather than sit on top of it. Shops can be restricted by job, gang or in-character licence.
• ph-houses: Property ownership and door definition, with house stashes and lockers supported across the major inventories including ph-inventory.
• ph-hud: Vehicle HUD and player status, with money, weapon, clock, player-info and postal elements, and a drag-and-drop HUD editor.
• ph-mechanic: Mechanic job with a redesigned admin panel, shop management and repair progression.
• ph-policeJob: Unified police job across Qbox, QBCore and ESX on the ox stack, with cuffing, escorting and a React NUI. The MDT ships as part of this resource rather than as a separate purchase.
• ph-multicharacter: Restyled character selector with an intro screen; Continue drops you straight back into your last character where you logged out.
• ph-invoices: Invoice and billing with a database-driven config, an in-game admin panel, and exports both into and out of the system.
• ph-radialmenu: Fully featured radial menu for QBox, QBCore, ESX, vRP and standalone.
• ph-vehicleshops: Vehicle dealerships with showrooms and dealer-managed stock. Currently alpha.
• ph-fishing: A fishing loop with a skill-based minigame, species tables by zone and time of day, rod and bait progression, and a market that reacts to supply. Early development.

On the road map

Ordered by release intent, not fixed dates. We publish a date when a build is in testing, not before.

1. Job framework: Multiplayer worksites with shared objectives, role assignment and progression that persists per player rather than per session.
2. Phyre bundles: Discounted collections for servers starting fresh, so you're not assembling a core stack one purchase at a time.
3. Full translations across the catalogue: Every resource shipping with PT-PT, PT-BR, ES, FR and DE locale files as standard.
4. Public changelog per product: Version history visible on each product page, tied to your Tebex package, so you can see exactly what changed before you update. The changelogs already ship inside each resource; this is about surfacing them on the store.

How updates reach you

Updates are pushed to your Tebex account automatically. You'll see them under your purchases, and breaking changes are always flagged in the version notes with a migration path, we don't ship a rework that silently eats your database.

If a resource is retired or replaced, existing customers get the replacement at no cost. That's been the policy since the first sale and it isn't changing.

Frequently asked

Does Phyre support QBox? Yes. ESX, QBCore and QBox are supported from the same build. The bridge is open so custom or heavily modified frameworks can be adapted.

Are the scripts escrowed? Yes, partially, and we're specific about which parts. The core logic ships under CFX asset escrow. Everything you'd actually want to edit is left open and unencrypted:

• Config: shared/config.lua and the rest of shared/, fully readable and commented.
• Locales: every language file, so you can translate or reword anything players see.
• Bridge / Custom layers: the framework, inventory and target seams (client/bridge/, server/bridge/, Client/Custom/, Server/Custom/). This is the layer you extend to support a custom or heavily modified framework, and it's deliberately outside escrow so you can.

In practice that means you can configure it, translate it and adapt it to a framework we don't ship support for, without ever needing the encrypted files. What's closed is the internal logic, the part that's the product.

If you hit a case where the open layer isn't enough to do what you need, open a ticket.

How long does delivery take? Instant. Purchases appear in your Tebex account immediately after payment.

Do I pay again for updates? No. Every resource includes lifetime updates for that resource.

Can I get support in Portuguese? Yes, support is available in Portuguese, English and Spanish.

Questions about anything on this list, or a resource you'd like to see built? Open a ticket in our Discord, road map priority is heavily influenced by what server owners actually ask for.