Everyone's talking about AI adoption. Almost nobody has the real numbers. Help us change that — and get the full report 👉 Engineers | Leaders

manual

Everything you need to know about Latent Patterns.

why latent patterns

Latent Patterns is an educational platform for developers learning AI concepts. It combines concise written technical guides with screencasts, presented in a focused monospace aesthetic designed to stay out of your way. No fluff, no filler — just the concepts you need, explained clearly.

getting started

  1. Sign in — go to /auth/login and choose either:
    • a magic link sent to your email, or
    • an available OAuth provider (for example Google, Microsoft, Okta, LinkedIn, or GitHub when configured).
  2. If you choose magic link — check your inbox and click the login link. Magic links expire after 15 minutes.
  3. Choose your access path:

authentication and sessions

Latent Patterns is passwordless. Magic-link sessions are stored in secure httpOnly cookies and last for 30 days by default.

If you open invite links (team invites or onboarding invites) while logged out, you'll be sent to /auth/login first and then returned to your invite flow automatically.

Social OAuth login is customer-scoped under the hood. Generic sign-in from /auth/login uses the default platform customer context. Invite and tenant-aware flows can resolve to a customer-specific OAuth context automatically without requiring you to manually enter tenant identifiers.

Enterprise admins can also share a dedicated tenant entrypoint: /enterprise/login/<customerId>. This opens customer-scoped social login directly and is useful for internal onboarding docs or IT runbooks.

courses

Content is organised into courses, each broken into sections containing individual lessons. Browse all courses from the homepage.

Lessons come in three formats:

Your progress is tracked per lesson. Mark lessons as completed to keep track of where you are in a course.

certifications

Some courses offer a proficiency certification upon completion. Certifications are industry-verifiable credentials you can share on your CV, LinkedIn, or personal website.

earning a certification

  1. Complete all lessons in a certifiable course.
  2. Pass all exit tickets (learning assessments) in the course.
  3. Go to /certifications and claim your certification.
  4. Choose a display name for your certificate (optional) and whether to show your email on the public verification page.

certification IDs

Each certification has a unique ID in the format LP-XXXXXX (for example, LP-A3F7C2). This ID appears on your badge and can be used by anyone to verify your certification.

verification

Anyone can verify a certification at /verify — no account required. Enter a certification ID to see its status, the course completed, and the holder's name (if provided). Verification is always public and free.

badges

Each certification includes an embeddable badge — an SVG image you can add to your website, GitHub README, or CV. The badge contains a verification URL that links directly to your public verification page. Badge status updates automatically (valid → expired) without any action from you.

From /certifications, use [download badge] to save the image, or [copy embed] to get an HTML or Markdown snippet.

six-month validity

Certifications are valid for 6 months. AI engineering best practices evolve rapidly — models, tooling, and techniques that are current today may be outdated in months. A six-month window ensures your credential reflects up-to-date knowledge.

Renewal is lightweight: your lesson progress stays, and you only need to re-pass the exit tickets to demonstrate you're current. Renew from /certifications when your certification approaches expiration.

portability

Certifications belong to you, not to your employer or your account. If you change jobs, your certifications come with you.

To enable portability, add a personal email to your account (prompted when you claim a certification, or anytime from /account). Once verified, any account — at any employer — that verifies the same personal email will automatically see your certifications. Nothing is transferred; your certifications are simply linked to your identity.

This means:

downloadable courseware

Some courses include downloadable pre-completed courseware. These downloads are complete reference implementations you can run locally instead of building incrementally during the lesson.

Downloads are available to active subscribers only. To start a download, use the course page link under download courseware. Download links are short-lived and single-use.

enterprise plans (billing + seats)

Enterprise billing starts at /enterprise/plans. Two plan types are available:

Enterprise plans are linked to your business email domain. Personal mailbox providers (Gmail, Outlook, Hotmail, Yahoo, iCloud, ProtonMail, and similar) are not eligible for enterprise checkout — you must use a company or organizational email address.

Only one active enterprise plan can exist per domain. If your domain already has an active plan, the purchaser will see an error and should contact the existing enterprise admin instead.

After purchase, the purchaser becomes the enterprise admin and can manage members, seat allocation, and billing at /enterprise/manage. Enterprise admins can also designate billing administrators — users who can manage billing (payment methods, subscription, seat counts) without consuming a seat or having access to subscriber content.

managing an enterprise plan

The enterprise management page at /enterprise/manage is available to enterprise admins only. It provides:

enterprise teams (identity + provisioning)

Separate from billing, Latent Patterns has a team identity model managed at /enterprise. Teams are domain-based and handle member provisioning, role management, and SCIM integration. A domain can have both a billing plan and a team simultaneously (a "hybrid" configuration).

Creating a team: Sign in with your company email and visit /enterprise. If no team exists for your domain, click "create team" — you become team admin automatically. If a team already exists, you join as a member instead. Personal email domains (Gmail, Outlook, etc.) cannot create teams. Each user can belong to only one team.

OAuth auto-create: When signing in via Google, Okta, or Microsoft from a new eligible domain, team ownership is initialized automatically — no manual creation step required.

Team admins can:

If your domain already has a team and you're not a member, ask an existing team admin for an invite. Duplicate teams for the same domain are intentionally blocked.

scim provisioning

SCIM provisioning is configured per provider from the /enterprise page. Supported providers are Google, Okta, and Microsoft Entra. Each provider is configured independently.

When you enable a provider for the first time, the system generates a unique SCIM endpoint URL and a bearer token. The token is displayed once — copy it immediately for your identity provider configuration. The endpoint follows the pattern /api/scim/<provider>/<tenantKey>/Users.

Token rotation: If a token is compromised or needs to be refreshed, use the "rotate token" action (requires confirmation). The previous token is immediately invalidated and a new one is displayed.

Disabling a provider: Disabling SCIM for a provider hides its endpoint and token. Re-enabling generates fresh credentials — the previous ones will not work.

When any SCIM provider is active for your team, manual team invites are disabled to avoid conflicting membership sources. Use your identity provider to manage team membership instead.

invites and onboarding links

Latent Patterns uses three invite flows for enterprise onboarding:

All invite links require authentication. If you click an invite link while logged out, you will be redirected to /auth/login first and automatically returned to the invite after signing in.

Each invite link is single-use. If a link is expired or already used, request a fresh invite from your admin.

interactive terminals

Some content pages include embedded interactive terminal sessions powered by Daytona sandboxes. These give you a real Linux terminal in your browser with full shell access.

[>] Try it out

You have 10 minutes with a live terminal. Try these:

▸ Check your environment
$ uname -a && whoami
See what OS and user you're running as
▸ Explore the filesystem
$ ls -la /
List the root directory
▸ Write and run a script
$ echo '#!/bin/sh echo Hello from Latent Patterns!' > /tmp/hello.sh && sh /tmp/hello.sh
Create and execute a shell script

how terminal sessions work

persistent workspaces

Your workspace (all files and changes) is saved for 7 days after your last session. When you return to the same terminal embed, your workspace is restored automatically — you pick up where you left off.

session recordings

Every terminal session is recorded. After your session ends, click [share recording] to get a link you can share with others. Recipients can watch a replay of your terminal session without needing an account. Recording links expire after 24 hours.

access levels

Terminal access depends on the content page. Some terminals require an active subscription, while others are available to any signed-in user. You must be authenticated to use any terminal — anonymous access is not available.

LLM usage and budgets

Terminal sessions include AI assistance (powered by Anthropic). Individual subscribers have a $1/day budget per terminal using the Haiku model. Enterprise teams with a BYOK (Bring Your Own Key) API key get access to all models with no daily limit — see the enterprise section below for setup.

enterprise API keys (BYOK)

Enterprise admins can configure Bring Your Own Key (BYOK) API keys for Anthropic and OpenAI. When a BYOK key is active, enterprise members get:

To manage your enterprise API key:

  1. Go to /enterprise/settings/api-keys
  2. Add an Anthropic key (starts with sk-ant-) for Claude models
  3. Add an OpenAI key (starts with sk-) for GPT models
  4. Keys are encrypted at rest and never exposed to users or browsers
  5. To rotate or disable, revoke the existing key and add a new one

Without a BYOK key, enterprise members use the platform defaults (Haiku model, $1/day budget) — the same as individual subscribers.

Revoked or rotated BYOK keys take effect quickly. In normal operation, terminal worker cache invalidation applies changes within seconds; fallback cache TTL ensures stale key usage remains bounded to a short window.

service health and status

Public uptime and incident updates are available at status.latentpatterns.com. Internal health checks include database, email, worker readiness (AI Grader, AI Chat, Playground, Terminal), and secret platform readiness signals for managed customer-secret infrastructure.

The public health endpoint is /health. It returns an aggregate status with ok, degraded, or error and includes:

Health responses are intentionally non-sensitive: they expose status labels only, never secret values, secret paths, or provider credentials.

enterprise SIEM integration

Enterprise admins can configure a SIEM (Security Information and Event Management) endpoint to receive real-time audit events for their organization. All authentication, content access, progress, and enterprise management events for members of your enterprise are forwarded to your SIEM.

Tenant isolation: Only events that belong to your enterprise are forwarded to your endpoint. Events from other enterprises or non-enterprise users are never included. This isolation is enforced at the application layer with defense-in-depth verification.

To configure SIEM integration:

  1. Go to /enterprise/settings/siem
  2. Enter your SIEM endpoint URL (must be HTTPS)
  3. Configure the authentication header name and value (supports Splunk HEC, Datadog, Microsoft Sentinel, and custom webhook endpoints)
  4. Use [test connection] to verify your endpoint receives events
  5. Enable forwarding when ready

Events are delivered as JSON via HTTP POST. Each event includes:

SIEM forwarding is supplementary — all events are always recorded in the Latent Patterns internal audit log regardless of SIEM configuration. If your SIEM endpoint is unavailable, events are retained internally and the configuration page shows delivery status.

Authentication credentials are encrypted at rest and never exposed to users or browsers. To rotate credentials, update the auth value on the settings page — the previous value is immediately invalidated.

glossary

The glossary is a standalone reference of AI and machine learning terminology. Each entry is a concise definition you can link to and revisit. Glossary entries are accessible independently of courses.

blog

The blog publishes short technical posts, release updates, implementation details, and architecture decisions that complement the courses. Past posts are archived at /blog. A dedicated RSS feed is available at /blog/rss.xml.

newsletter

The newsletter is a separate publication from the blog. Subscribe with your email at /newsletter or via the signup component found around the site. A confirmation link is sent to your inbox — click it to activate your subscription.

Past newsletter posts are archived at /newsletter. A dedicated RSS feed is available at /newsletter/rss.xml.

You can manage your newsletter subscription from the account page email preferences, or via the unsubscribe link included in every email.

patterns

Patterns is a separate publication focusing on recurring patterns in AI engineering, agents, and practical systems. Past posts are archived at /patterns. A dedicated RSS feed is available at /patterns/rss.xml.

You can manage your patterns subscription from the account page email preferences, or via the unsubscribe link included in every email.

rss

You can subscribe to any of our publications in a feed reader:

email preferences

Latent Patterns sends email across four categories: newsletter, product updates, course activity, and marketing. Each category can be toggled independently.

You can manage your preferences in two ways:

There is also a one-click "unsubscribe from all" option that disables every category at once.

pricing

Latent Patterns has two commercial paths:

Payments are processed securely by Airwallex.

knuth award checks

Inspired by Donald Knuth's tradition of issuing reward checks for finding errors in his books, Latent Patterns awards digital checks to users who report content errors.

how it works

  1. While reading a lesson or glossary entry, select the text containing an error.
  2. Click [report problem] in the popover that appears above your selection.
  3. Describe the error in the feedback form and click [submit].
  4. If verified, you'll receive a Knuth check — a digital certificate from the fictional Bank of Kangaroo Island.

check values

Following Knuth's original system:

Values are symbolic — a collectible status item, not real currency. Most Knuth check recipients frame them rather than cash them.

what counts as a reportable error

check IDs and verification

Each check has a unique ID in the format LP-XXXXXX. Anyone can verify a check at /knuth — no account required.

sharing

Each check includes a shareable verification page with links to share on X, Bluesky, LinkedIn, and Facebook. You can also embed an SVG check image on your website or CV.

leaderboard

The Knuth checks leaderboard ranks contributors by total value earned. Your checks and total are also displayed on your account page.

referral program

Active individual subscribers can earn 1 free month of subscription time for each friend they refer who subscribes. Enterprise members are not eligible for the referral program.

how it works

  1. Go to your account page — you'll see a referral program section with your unique referral link.
  2. Share your link with friends. It looks like latentpatterns.com/r/XXXXXX — a short, easy-to-share URL.
  3. When someone visits your link and signs up, their account is linked to yours as a pending referral.
  4. When that person subscribes, your referral is credited — 30 days are added to your current billing period automatically.

referral stats

Your account page shows three referral metrics:

There is no limit on the number of people you can refer. Each successful referral adds another 30 days to your subscription.

lapsed subscriptions

If your subscription has lapsed (canceled or past due), your referral code still works. When someone you referred subscribes, your subscription is reactivated with a fresh 30-day period — no payment needed. Additional referrals stack on top, extending your reactivated subscription further.

account

Your account page is your control panel for subscription, enterprise membership, email preferences, and access to related pages.

The account page shows:

From account, quick links take you to:

billing

The individual billing page is available when you have an active individual subscription. It shows subscription status, billing period end, and whether the subscription is set to cancel at period end. From there you can update your payment method or cancel your subscription.

The enterprise billing page is available to enterprise admins and billing administrators. It shows enterprise plan details (domain, status, seat usage, billing period) and allows:

rate limits

API endpoints, authentication, support, and newsletter routes are rate-limited by IP address using a 1-minute sliding window. Content browsing routes are not rate-limited. Limits are designed to support large concurrent usage — for example, an enterprise classroom with thousands of students accessing the site from a shared network.

If you exceed a rate limit, you'll receive a 429 Too Many Requests response with a Retry-After header indicating how many seconds to wait before retrying.

support

If you run into a problem or have a question, open a ticket from /support while logged in.

Prefer email? You can also reach us at support@latentpatterns.com.