Your business.
Your software.
Your accounts.

1. Create your account and verify your email

   Sign up at github.com/signup using a business email you control. Verify the address so repository and security notices reach you.

2. Enable two-factor authentication

   Use an authenticator app or passkey, add a backup method, and store your recovery codes somewhere safe. GitHub strongly recommends 2FA and may require it for code contributors.

3. Create an organization you own

   In GitHub, open your profile picture, then Settings → Organizations → New organization. Choose the free plan unless you already need paid features. Name it for your business. For a substantial project, the organization keeps repositories, teams, and billing together. For a small first project, a personal account can work, but the account must still be yours.

4. Invite Hank

   Open the organization, then People → Invite member. Use the identity from your engagement email. If we will create repositories and configure organization-level automation, invite us with the Owner role. If you prefer tighter access, invite us as a member and grant Admin access to the project repositories instead. We will confirm which is needed during scoping. Invitations expire after seven days.

5. Keep independent owner access

   You remain an organization owner, and at least one other trusted person should be an owner for continuity. We never need to be the only owner, and you can remove our access whenever you choose.

Verify your GitHub email Configure two-factor authentication Create an organization Invite an organization member Organization roles GitHub plans

1. Create your account and secure it

   Sign up at dash.cloudflare.com/sign-up. Verify your email, then enable two-factor authentication and save the backup codes. Keep the account in the business's name.

2. Add the domain and review imported records

   In the Cloudflare dashboard, choose Add a site, enter your domain, and select the Free plan to start. Cloudflare scans and imports your existing DNS records. Review them before changing nameservers—especially MX, SPF, DKIM, and DMARC records that keep business email working.

3. Update nameservers at your registrar

   Cloudflare assigns two nameservers. Add both at your registrar. If DNSSEC is enabled, turn it off at the registrar before the change and re-enable it in Cloudflare after the domain is active. Your registration stays with your registrar; nothing needs to be transferred.

4. Decide on billing when the project requires it

   The Free plan covers DNS and basic services. Workers Paid starts at $5 USD a month for the account and includes 10 million requests and 30 million CPU milliseconds a month; overages are billed at published rates. D1 database and R2 storage usage may add charges. Add a payment method only when the approved scope calls for it.

5. Invite Hank with project-level permissions

   In the dashboard, open Members → Invite members. Use the email from your engagement correspondence. For most projects, grant a policy scoped to the whole account with the Administrator role—full account access, but not member management or billing-profile control. If you prefer tighter access, use a scoped policy with Workers Platform Admin and Domain DNS. Keep yourself as Super Administrator - All Privileges.

6. Keep ownership and deployment credentials separate

   You retain member management and billing. We create scoped API tokens only where automation requires them and store them as repository secrets. Never send a Global API Key or your account password.

After the handoff, we create and configure Workers, databases, storage buckets, custom domains, HTTPS, deployment tokens, and CI/CD. We document what exists and how it is deployed.

Add a domain Manage account members Account roles Workers pricing Cloudflare two-factor authentication

1. Create your account and protect it

   Sign up at openrouter.ai/sign-up, verify your email, and enable two-factor authentication under Settings → Preferences → Security.

2. Create an organization if the project needs one

   Go to Settings → Preferences. In the Organization section, choose Create Organization and follow the setup. Organizations are separate from personal accounts and share a credit pool; they currently support up to 10 members. A personal account may be enough for a small pilot, as long as you control it.

3. Add your own payment method or credits

   Open Settings → Credits and add credits with your own payment method. Auto top-up is optional. Model prices vary, so review current pricing before approving a production feature.

4. Set a sensible budget and alerts

   In the workspace, open Guardrails and create a guardrail with a budget limit that resets daily, weekly, or monthly. Requests are rejected when the limit is reached. In Settings → Notifications, enable the low-balance alert and, for each key, the API key spend-limit alert. Alerts warn you; budgets stop spending. A very low hard limit can interrupt a working application, so choose it with the project's expected usage in mind.

5. Invite Hank as an organization admin

   In the organization's member settings, invite the identity from your engagement email with the Admin role. Keep yourself as an administrator and keep control of billing. If you use a personal account instead, share only the keys and access the project requires.

Organization management Spend controls Guardrails Notifications and alerts Workspaces