Diagnose your install.
Answer three things, paste the error if you have one, and get a grounded read. Live products get full install and troubleshooting support; products still in development give a pre-purchase compatibility check only. Secrets are stripped before anything is diagnosed — the box warns you, and the server strips again as a floor.
The live concierge runs on the full store, which isn't open yet.
Until then: check the troubleshooting index (grouped by the error you're seeing), or email support@vicedrip.com with the product, your framework, and the error — minus any keys or passwords.
Installing a FiveM resource is order, dependencies, and a database.
The Concierge is built to read each of those surfaces from your actual output. Paste a log or a config block and it grounds every step in the product's docs.
server.cfg review
The most common reason a resource won't start: ensure lines, start order, and dependency order. Tell the Concierge where it sits in your cfg and it checks the ordering against the product's docs.
Console-log troubleshooting
Paste the server boot error or the F8 client error and it reads your actual output — not a generic FAQ. You get the likely cause, ordered fix steps, and the files to check.
SQL install
oxmysql connection, schema import, and the missing-table errors that follow a half-run .sql. It walks the import and points at the exact line that failed.
Framework compatibility
Qbox, QBCore, ESX Legacy, or standalone — the bridge is checked before you commit. For products still in development this is the whole answer: a pre-purchase compatibility read.
Config review
The config key set to the wrong value before it becomes a runtime error. Paste the config block and it flags the setting that doesn't match your framework or your economy numbers.
The rails on the paste box.
Escalation is one click
Every diagnosis ends with a human hand-off. Low confidence, anything touching money integrity or licensing, or a repeat failure routes to a person automatically. It never guesses when the docs don't support an answer.
Secrets are stripped, never requested
The paste box warns you, and the server strips again as a floor. We never ask for passwords, license keys, database credentials, or API tokens — and you should never paste them. A ticket carries a redacted summary, never a secret.
It won't claim your server is fixed
This is a deterministic, doc-grounded read, not a promise. You mark what's fixed; the engine never claims success for you, and nothing is called resolved without a fresh log. It does not fix every issue, and it says so when it can't.
Prefer a person from the start? Submit a ticket → Secrets are stripped before anything is stored.
White-Glove Install.
Hands-on · a request, not a checkoutWant a live product stood up with you — server.cfg wired, database imported, framework bridge confirmed, config tuned to your numbers, ending in a clean boot log? A hands-on install service does exactly that. You hold the licenses and perform every privileged action; we never handle your credentials, and there is no unattended access. It is a request that routes to a human — never an instant purchase, and not an uptime guarantee.