ZipLoom
Home
PricingSign InGet Your Live URL

security

Two-Factor Authentication

TOTP 2FA On Every Sign-In, Before Your Code Security Even Runs.

Updated

At a glance

ZipLoom requires TOTP two-factor authentication on every account and every sign-in — the account security layer that comes before code security.

  • Works With Any Authenticator App
  • Mandatory, Not Optionally Enabled
  • Account Security Before Code Security
Sample. Every sign-in to ZipLoom needs your password plus a 6-digit code from your authenticator app, set up on your first sign-in before anything else.

Why it matters

Every check ZipLoom runs on your code assumes the person deploying is you. If someone signs in with a leaked password, they can ship their own code to your domain, and the deploy looks completely normal.

That is why two-factor is mandatory here rather than a setting. Every account enrolls an authenticator app before it reaches the dashboard, every sign-in asks for a code, and the second factor is checked on the server for every API request and in the database itself. It works with any standard authenticator app, is a one-time setup per person, and comes with ten single-use recovery codes for the day a phone goes missing.

Two Keys To Your DeploysIllustration · sample data
Password••••••••482917app codeEvery API callchecked againDatabasechecked again10 codesone use

What you get

Works With Any Authenticator App

Standard TOTP (RFC 6238). Google Authenticator, Authy, 1Password, Bitwarden, Apple Passwords — any app that generates 6-digit time-based codes works. No proprietary app required.

Mandatory, Not Optionally Enabled

Every account sets up two-factor before it can reach the dashboard, and every sign-in requires the second factor. Not a setting anyone can quietly disable. Assurance Level 2 (aal2) is checked server-side on every API request — and in the database itself.

Account Security Before Code Security

A compromised account bypasses every code-level security check. 2FA addresses the layer below the deploy scanner — it stops an attacker from reaching the deploy interface at all.

How Enrollment Works

  1. 1

    On your first sign-in, ZipLoom asks you to set up two-factor before anything else.

  2. 2

    Scan the QR code with your authenticator app.

  3. 3

    Enter the 6-digit code to confirm enrollment.

  4. 4

    From this point, every sign-in requires your password plus a code from the app.

  5. 5

    Ten single-use recovery codes are generated at enrollment and shown once. Store them somewhere safe — they're the only way back in if you lose your device. Add a second authenticator in Settings → Security before removing your first.

What this check inspects

  • Whether two-factor authentication is enforced on the accounts that can deploy.

  • Which members hold deploy rights, and whether those rights match their role.

  • Session and token settings for the deploy platform connection itself.

  • Audit records for who deployed what, and when.

What it means when this fails

Your deploy platform holds the keys to production. An account takeover there is worse than a bug in your code: it lets someone ship their code as you, to your users, on your domain — and the deploy looks entirely legitimate.

What it does not do

  • It protects your ZipLoom account, not your GitHub account or your hosting accounts. Turn on two-factor there as well.

  • It is TOTP from an authenticator app. Single sign-on is not available.

Questions

Isn't 2FA on GitHub enough?
GitHub protects the repository. The deploy platform is a separate account with separate credentials and its own path to production.
Does this slow the team down?
It's a one-time setup per person. Compared with recovering from someone else deploying to your production domain, it's nothing.
What if a member loses their device?
Owners can reset access for the organization; the audit log records the change.

What it replaces

Doppler Team

Dedicated secrets manager with SSO, RBAC, and rotation. Free for 3 users; separate from your deploy.

$21/user/mo

GitHub Advanced Security (both)

Code Security + Secret Protection together, per active committer.

$49/committer/mo

Vanta

Compliance automation (SOC 2, ISO 27001). Audit fees are separate. Quote-based.

from ~$6,000/yr

ZipLoom Solo — every deploy check included

Deploy, security scan, and monitoring in one flat price. Guild $40/mo · Studio $70/mo · LoomWorks $149/mo · Business $299/mo.

$216/yr($20/mo)

Related features