FAQ
Start with the toolkit docs for exact setup steps. These answers cover product fit, availability, common setup checks, and what to include when you contact support.
Find the right toolkit.
Which toolkit should I start with?
Choose the backend you already use: Supabase, AWS, or Firebase. The License Toolkit is for auditing third-party package and asset licenses; it is not a backend.
Do ShipIt toolkits host my backend or handle my players’ data?
No. The backend toolkits connect your Unity project to the provider project and services you control. ShipIt does not operate an application server in that data path. Your provider’s usage and billing are governed by that provider’s account and terms.
Which Unity versions are supported?
The current site lists Unity 2022.3 LTS or newer for the Supabase, AWS, and License toolkits. The Firebase Toolkit lists Unity 6.3 LTS or newer. Check each product page before installing, since requirements can change with releases.
Buy and get started.
Which products can I buy today?
The ShipIt Supabase Toolkit is listed on the Unity Asset Store. AWS, Firebase, and License are currently marked pre-release. Check Where to buy for the latest listing status.
Where do I download a toolkit after buying it?
For a purchased Asset Store package, open your Unity Asset Store purchases and import it into the project using Unity’s package workflow. Follow the matching Supabase documentation for its current installation steps. The other three toolkits are not yet listed for purchase.
Do I need to pay for the backend provider too?
You need your own provider account and project for live backend use. Provider services may charge for usage under their own plans and terms. Check the provider’s current pricing and the toolkit’s prerequisites before building around a service.
Is the License Toolkit legal advice?
No. It produces license and attribution findings with evidence to help you review a project. Its results are informational and do not replace legal advice or your own review of the relevant licenses.
A few checks before support.
The package or setup wizard is failing. What should I check?
Confirm your Unity editor meets that toolkit’s stated minimum version, make sure you are following the documentation for the package version you installed, and check the provider-specific prerequisites on its product page. Start with the first relevant Unity Console error; later errors may only be follow-on symptoms.
Use the product-specific setup guide: Supabase, AWS, Firebase, or the License quick start.
What information helps support reproduce an issue?
Include the toolkit name and version, Unity editor version, operating system and target platform, the steps that reproduce the issue, and the first relevant Console error. A small sample or a redacted screenshot can help when it shows the problem clearly.
What should I leave out of a support email?
Do not email passwords, service-role or secret keys, access tokens, recovery codes, or private customer data. Redact those values from screenshots and logs before sharing them. See the Privacy page for how support messages are handled.