Sign up

Signing up is four steps, in this order: account → workspace → trial → setup. Nothing after the first step needs anything you have not already given your sign-in provider.

Unless a colleague has already signed Nodrik up. If they have, none of this page is your route in: ask them to invite you from Team ▸ Invite a colleague and follow the link in the email. An account belongs to exactly one workspace, so signing up separately and asking to be merged afterwards is not something the product can do for you — and a second workspace on the same estate does not get its own trial either. What the invite gives you, and what each role can do, is on Your team.

1. Account

Go to console.nodrik.dev/start and continue with Google or GitHub — either one reaches the same workspace, and there is no separate password to set. If you use GitHub, it needs an email address the console can read; sign-in is refused otherwise, and GitHub → Settings → Emails fixes it in about a minute.

Signing in with GitHub is only about who you are. It gives Nodrik no access to a repository — that is a separate installation you choose later, and it is covered on Connect GitHub.

Sign in with Google once and with GitHub later, on the same address, and the two are joined into one account rather than becoming two — Nodrik asks you to prove the first provider before it links the second. Two different addresses stay two different people, deliberately: no provider promises us that an address it reports has been verified, so we never treat a matching address as proof of anything on its own.

2. Workspace

Your workspace is created automatically once you sign in — a tenant, a dedicated service account, and the Firestore records that hold your configuration. You are not asked anything at this step; it runs in the background while you move on to choosing a plan.

You are its admin, because somebody has to be able to pay. Colleagues you invite later can be admins too, or members, or read-only — see Your team.

3. The 14-day trial

Every plan, in full, for 14 days:

• Card required, $0 charged today. Stripe collects a card up front so the trial can start immediately; nothing is charged until day 15.
• First charge on day 15, unless you cancel first.
• Cancel any time during the trial with nothing owed.
• One trial per estate, ever. A workspace that has already trialled — including one you skipped — does not get a second free 14 days, and neither does a fresh workspace on the same Google Cloud organisation, the same monitored projects, or the same card. What we keep in order to check this is a one-way hash of each, and nothing else: Security and trust sets it out, and so does the privacy policy.

You can pick a tier now or choose “Skip for now.” Skipping does not delete your workspace; it stays exactly as it is, and Nodrik simply will not investigate anything until a plan exists. You can start the trial later from Home.

Tier prices, capacity and fair use are on the pricing page and repeated, from the same source, on Plans and billing.

If the trial is refused

You are told, on the spot, before you pay anything — this never happens quietly. Checkout then carries on without the trial: you can subscribe today at the ordinary price, starting today, or close the tab and owe nothing. Nothing is charged by the act of being refused.

If the estate only turns out to have trialled after you have completed checkout, the subscription is cancelled rather than billed. The first invoice on a trialing subscription is $0, so a cancellation at that point costs you nothing at all.

A returning customer — somebody who has subscribed before, or whose subscription lapsed — sees none of this. They were not offered a trial to lose, so nothing is said about one; checkout is simply the ordinary checkout.

If you think a refusal is wrong, or you have a real reason to want a second trial on the same estate, tell us — releasing a claim is something we can do.

4. Setup — never gated on a plan

This is the part worth stating plainly: granting access, connecting Slack and connecting GitHub cost nothing and commit to nothing. You can do all three whether or not you have started a trial, and whether or not a previous trial has ended. Only one thing is gated on having an active plan — running a real investigation (including the setup checklist’s test alert), because an investigation spends real model tokens.

The setup checklist covers, in the order most people do them:

1. Connect a Google Cloud project — grant Nodrik the four read-only roles it needs, on the projects you choose.
2. Connect Slack — pick the channel Nodrik posts to.
3. Connect GitHub — optional, sharpens “what changed?” answers.
4. Send a test alert, and watch the report land in Slack.

Every item on that list is reachable at any time from the console’s Home screen — it is a list, not a locked sequence, so there is no wrong order to do it in.

If you subscribed and then stopped paying

A payment that fails on an established subscription changes nothing while Stripe retries it — Nodrik carries on investigating, and you are not in a grace period. Only when Stripe gives up does the subscription lapse. (A card that fails on the first charge, at the end of a trial, lapses straight away: there is no established subscription behind it.)

A lapsed subscription keeps everything connected for 30 days: monitored projects, Slack, GitHub, and your workspace configuration. Home shows a banner with Subscribe (your previous tier, pre-selected, no second trial), Change plan, and Leave. Nothing is investigated during the grace window, and nothing is deleted until it ends. Detail in Plans and billing.