itemlogs — Documentation
What this does
When you register at itemlogs.com, you paste in a Vercel personal access token (generated at vercel.com/account/tokens, step 2 of the registration wizard). We use it, via a small runner service that runs the real Vercel CLI on your behalf, to create a new Vercel project, attach Blob storage and a Supabase database to it, set the AUTH_SECRET environment variable, and deploy your inventory — all automatically, in one pass.
What you still do yourself
Just two things, both one-time: generating the access token itself, and — the first time ever that your Vercel account connects a Supabase database — approving a one-time Marketplace terms page Vercel puts in front of you, in a new tab. The registration wizard walks through both. Everything else (Blob, Supabase, environment variables, the deploy itself) happens without you touching the Vercel dashboard.
Once registered, itemlogs.com/setup/<your-inventory-name> shows a live status snapshot of your inventory — useful if a deploy is still in progress, or if something needs a follow-up look.
Environment variables
AUTH_SECRET | Set automatically during registration. |
SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, POSTGRES_URL | Set automatically when Supabase is attached during registration. |
BLOB_READ_WRITE_TOKEN | Set automatically when Blob is attached during registration. |
Revoking access
The access token you generated is what lets us set environment variables and trigger redeploys for your project — revoke it at any time from vercel.com/account/tokens (delete the token you created during registration). This does not delete your inventory or its data — it only stops us from being able to push further environment variable updates or trigger redeploys for you.
Questions
See /contact, or the Privacy Policy for how your data is handled and the terms of using this service.