Get started with Torque Lift
What to have ready, the one setup command, and the two pull requests you merge before your first readout arrives on day 14.
One engineer runs one command in your app's repo. Your growth lead reviews two pull requests. Your first readout arrives from day 14.
In our timed runs, the command took under 3 minutes from the first question to "your part is done". We ran them ourselves, so a first run by someone new will take a little longer.
What to have ready
Torque Lift is working with a small group of early partners. Once you're in, we send you a setup code. You need:
- A repo on a supported stack. Web apps on Next.js, React with Vite, Remix or React Router, with a committed lockfile, tests on Jest or Vitest, and CI that runs on pull requests. Android (Kotlin) and iOS (Swift) are in early testing.
- Permission to install a GitHub App on that repo. If you can't, the command gives you a page to send to an owner.
- An AWS account of yours. Today your events land in a bucket there. You need the 12-digit account ID, and someone with admin rights in the account for one click.
- Node.js 20 or newer and a terminal open in the repo.
The command checks your repo against these first, and says which check fails. Torque Lift opens pull requests only where your default branch requires a pull request with an approval, so a person on your team always decides.
From setup code to first readout
Run the setup command
npx https://torquelift.ai/cli/torque-lift.tgzThe command signs in with your setup code, then asks for your AWS account ID and opens the AWS page with everything filled in. Your AWS admin ticks one box and clicks Create stack. While AWS builds your stack, you install the Torque Lift GitHub App on your repo only. Then you name the GitHub logins that can sign in to your console.
Prefer a coding agent? Paste it this line, with your code: "Follow the instructions at https://torquelift.ai/cli/setup.md to set up Torque Lift for this repo."
Merge the tracking plan
Torque Lift opens a pull request titled "Torque Lift: review your tracking plan". It adds one file, torque-lift/tracking-plan.yaml, listing up to 10 events. It changes no app code.
Merging it is your growth lead's approval of the plan. See Tracking for what the file holds.
Set the environment variables, then merge the tracking
A second pull request adds the tracking itself. It lists the environment variables to set in production before you merge, and how to check afterward that events arrive. The code it adds is described in Code in your repo.
Sign in to your console
Use GitHub at console.torquelift.ai, as one of the logins you named. The Data page shows whether events are arriving and what was turned away.
Read your first readout
It arrives from day 14, once your first full week has closed. See Readouts for what is in it.
What the command never does
- It never asks for AWS keys, passwords or GitHub tokens.
- It runs only git and read-only AWS calls, and never runs your repo's code or package manager.
- It saves a sign-in token for this machine in
~/.config/torque-lift/setup.json, outside your repo, for 30 days.
The full list of what you allow, and what Torque Lift can't touch, is in Data and privacy.
Bring in your past events
Setup is complete without them. To import history from PostHog, Mixpanel, Amplitude or Segment, run this when you're ready. It takes 15 to 30 minutes.
npx https://torquelift.ai/cli/torque-lift.tgz historyType a secret yourself
If your tool needs a secret, you type it into your own terminal, twice. It isn't shown. Never send it by email or chat, and never give it to a coding agent.
If something goes wrong
If the command stops or you close it, run it again. It checks each step against our record and carries on where it stopped. A setup code works once and lasts 7 days. More in Troubleshooting.