Every surface

A library, a CLI, a TUI and an MCP server where it makes sense. Humans get a terminal, agents get a tool, and both call the same code.

02

Agent native

Written for the agentic era. The whole stack is one curl away as Markdown or JSON, so an agent can read the rules before it writes a line.

03

Proven in production

Nothing here is a demo. Each package was pulled out of a live product after a second product needed it, and the fleet still runs on it.

04

Open and portable

MIT licensed, on npm, self hostable. Bare metal or Railway, Turso or Postgres. No vendor holds the keys.

The libraries

Every one is on npm under MIT. Pick the pieces you need; they do not require each other.

Build

The app layer: shared modules, accounts, data, terminals and media.

Stack

Shared modules for Next and Node apps: referrals, email, payments and CrawlProof in one import.

Lib

npm GitHub@profullstack/stack

HQ TUI

btop-grade terminal dashboards for TypeScript from a one-import API. Dark by default.

LibTUI

npm GitHub@profullstack/hqtui

Orgs

Organizations, teams, members, roles and invites for Postgres. Bring your own users table.

LibCLI

npm GitHub@profullstack/orgs

Bridges

Let a host site's signed-in users into an app over OAuth 2.1 with PKCE. No second signup.

Lib

npm GitHub@profullstack/bridges

libSQL PG

A drop-in @libsql/client that talks to Postgres, plus the tools to move a Turso database over.

LibCLI

npm GitHub@profullstack/libsql-pg

Player

One web player for MP4, HLS, MPEG-TS and audio, with one control bar.

Lib

npm GitHub@profullstack/player

Form Guard

Contact-form spam stopped with a signed proof-of-render token. No captcha.

Lib

npm GitHub@profullstack/form-guard

Browser Fingerprint

One vote per browser, not per IP: a salted device fingerprint, a signed challenge, a bot score and limits for anonymous writes.

Lib

npm GitHub@profullstack/browser-fingerprint

Submit Feed

One way to add a feed to a directory, shared by every site that takes one.

Lib

npm GitHub@profullstack/submit-feed

Scraper Daemon

One updater daemon for every listing site: jobs, refresh queues and resumable pipelines, polite and SSRF-safe fetching, SQLite or Postgres state.

LibCLI

npm GitHub@profullstack/scraper-daemon

Agents

Tools an agent can drive: MCP servers, data bridges and documents it can read.

MCP Server

A generic, modular server for the Model Context Protocol. Add a module, get a tool.

MCP

npm GitHub@profullstack/mcp-server

NicheDB

Browse collections, manage sources and feeds, and search datasets from a terminal or an agent.

CLIMCP

npm GitHub@profullstack/nichedb

media2md

Turn any video, audio file or book into a chaptered Markdown bundle you can hand to an LLM.

CLIMCP

npm@profullstack/media2md

OpenProfile

Read, write, merge and de-duplicate OpenProfile.md documents for people and agents.

Lib

npm GitHub@profullstack/openprofile

Profile

One signup profile for every property: email, name, company domain, job title and LinkedIn, in the order sales tools import them.

LibCLIMCP

npm GitHub@profullstack/profile

Agentic Jobs

An agent-friendly job board you self host. It posts its own jobs and never scrapes anyone else's.

App

npm GitHub@profullstack/agenticjobs

Proxy

Call the web through residential proxies, with each provider behind one interface.

LibCLIMCPTUI

npm GitHub@profullstack/proxy

Money

Get paid by people and by machines: crypto checkout, x402 and pricing instead of 429s.

CoinPay

Non-custodial crypto payments: BTC, ETH, SOL, USDC and more, with x402 verify and settle.

LibCLITUI

npm GitHub@profullstack/coinpay

x402 Gateway

Sell crawl access to AI training crawlers by the day over x402. Next and Hono adapters.

Lib

npm GitHub@profullstack/x402-gateway

x402 Client

Pay x402 402s from JavaScript with a local key: a fetch, a CLI, and axios and got adapters.

LibCLI

npm GitHub@profullstack/x402-client

Throttle

An app-wide rate limit whose answer to going over is a price, not a 429.

Lib

npm GitHub@profullstack/throttle

Keys

Ed25519-signed Power Keys: one key that unlocks every Profullstack service.

Lib

npm GitHub@profullstack/keys

Referrals

A referral program SDK: 60% to the affiliate, 20% off for the new customer.

Lib

npm GitHub@profullstack/referrals

Affiliates

Scarce, single-use invite codes with a per-user quota, plus affiliate links with first-touch attribution.

LibCLI

npm GitHub@profullstack/affiliates

Redeem Credits

Scarce, hashed codes that redeem for one-off or monthly credits, with a balance to spend against.

LibCLI

npm GitHub@profullstack/redeem-credits

Ship + operate

Release everywhere, watch everything, and keep the fleet up without a pager.

sh1pt

One codebase to every store, registry, CDN and channel. Build, promote, scale, iterate.

CLI

npm GitHub@profullstack/sh1pt

ThreatCrush

An all-in-one security daemon: monitor, detect, scan and protect servers in real time.

CLITUI

npm GitHub@profullstack/threatcrush

CrawlProof

What the fleet costs and what it returns, in a live terminal dashboard over your traffic.

CLITUI

npm GitHub@profullstack/crawlproof

Watchdog

Notice when Postgres or Redis stops answering, and exit so the platform restarts you.

Lib

npm GitHub@profullstack/watchdog

Encrypt

Quantum-resistant encryption: ML-KEM-1024 plus ChaCha20-Poly1305, wire compatible with qrypt.chat.

LibCLIMCP

npm GitHub@profullstack/encrypt

Emailer

Transactional and bulk email through Resend. No SMTP or Gmail transport.

Lib

npm@profullstack/emailer

Every package

All 353 packages in the @profullstack npm scope and all 263 public repos, regenerated from npm and GitHub. Agents read the same list at /stack.md.

Build 53The app layer: shared modules, accounts, data, UI, terminals and media.

Agents 18MCP servers, agent tooling and documents an agent can read.

Money 15Crypto checkout, x402, credits, referrals and invoices.

Ship + operate 15Deploy, secure, watch and keep the fleet up.

Product clients 28The CLI, TUI or MCP client for one Profullstack product. Use it to drive that product, not as a library.

sh1pt adapters 208Plugins for sh1pt. Install them through sh1pt, never on their own.

Uncategorised 16Published, not yet sorted. Read the README before depending on one.

Public repos without a package 122Apps, sites and tools whose source is public on GitHub.

Start with a prompt

The whole stack, its combos and its house rules are published as text for agents. Point Claude Code, Codex or any agent at it and it builds the way we do.

stack.md stack.json Build an app skill.md

Blueprint updated 2026-10-29

$ curl -fsSL https://profullstack.com/install.sh | sh
# the Profullstack skill, into every agent on the box

$ curl -s https://profullstack.com/stack.md

> Build me a waitlist app on the
  Profullstack stack. Read
  https://profullstack.com/stack.md
  first and follow the house rules.

The blueprint

Profullstack runs about 170 active repos on a small number of deliberate combinations. Pick the combo that matches the job, inherit the shared defaults, follow the house rules, and reuse the published packages before writing anything new.

Pick a combo

There is no single stack. Match the job to a combo, then apply the shared defaults and the house rules.

A new product with a web UI

web-app Next 16 on Turso with a Hono API inside the app. This is the default for anything new.

A change to an existing SaaS on Supabase or Postgres

web-app-postgres Stay on the database it has. Do not migrate an app to Turso as a side effect of a feature.

A real-time 3D game, in the browser and on the desktop

games Babylon on a pure rules core, server-authoritative multiplayer, and art generated by committed scripts rather than modelled by hand.

An API, crawler, poller or data service with little or no UI

api-service Hono on Turso, Bun or Node, one Railway service with a health check.

A command-line or terminal tool, or an agent-facing bridge

cli-tui Node, TypeScript, commander, hqtui for dashboards, MCP where an agent should drive it, published to npm.

A desktop app

desktop Electron with the CLI bundled inside it, so one install gives both surfaces.

A mobile app

mobile Expo inside the product monorepo, sharing the API and packages.

Code two or more products need

library A runtime-neutral @profullstack/* package with subpath exports, released from GitHub.

Something that must be a single fast binary

systems Rust (tokio, axum, clap), or Go when the upstream ecosystem is Go.

Shared defaults

Every combo inherits these. A combo below only lists where it differs or adds.

Concern	Choice	Notes
Language	TypeScript, ESM	"type": "module" everywhere. Kebab-case filenames, semicolons, printWidth 100. JavaScript with JSDoc is fine in small packages.
Runtime	Node 22 or 24 (floor is 20)	Bun 1.4 where the repo pins it in packageManager. Runtimes are managed with mise on dev boxes.
Package manager	pnpm, pinned in packageManager	Bun on Bun repos. Never mix lockfiles. Workspaces via pnpm-workspace.yaml for monorepos (apps/, packages/, services/).
Hosting	Railway	One project per product, railway.json per service with healthcheckPath, deploys on push to the default branch. Custom domain before any URL is written down.
Web server	Caddy	Hosts, reverse proxies and static sites with automatic HTTPS (it gets and renews certificates itself) and IPv6 on by default. Its localhost admin API lets agents and the w3bs CLI add a site without editing config. The default web server on W3BS OS and in front of pit.world and Moshpit names (moshpit-proxy). nginx boxes keep nginx until they are moved.
DNS	Porkbun	No Cloudflare DNS requirement.
Secrets	logicsrc team vault + Railway service variables	Set on the service, record in the vault. No .env files in repos; a framework-required .env.local is a local cache, never the source.
Auth	Magic link + passkeys	The magic link doubles as signup. Passkeys via @simplewebauthn. An optional password only for devices that cannot open mail or hold a passkey (TVs).
Email	Resend + @profullstack/email-queue (in development)	Resend is the intended application provider. The shared queue source is not published and is not yet deployed portfolio-wide. PostgreSQL audit integration, service API, CLI, MCP, admin PWA, production monitoring and migrations remain incomplete. Gmail sending is restricted to approved one-off use.
Payments	CoinPay (crypto) and x402	Crypto through @profullstack/coinpay. x402 sells access to agents and crawlers, settled by CoinPay. No Stripe and no card checkout.
Crawler policy	@profullstack/x402-gateway + @profullstack/throttle	Training crawlers get 402 with a daily pass to buy, robots.txt is generated from the same lists, and every route is limited to 100 req/min with a price instead of a 429.
Media playback	@profullstack/player	Every audio and video player: MP4, HLS, MPEG-TS and audio with one control bar. `attachSource` when a site keeps its own UI. A third-party player bump that breaks means move to it, not migrate the old player.
Modern CSS	@profullstack/modern-css	Subgrid cards, squircle corners, stuck headers, grid gap rules, height:auto accordions, reading-flow and @function helpers (--fluid, --alpha, --inner-radius) as opt-in classes in the components layer. Reach for these before JS or extra DOM. Every one is progressive enhancement: write the plain value first.
Analytics	CrawlProof stats.js	Every public site loads crawlproof.com/stats.js. Careers pages are fed from CrawlProof.
Referrals	@profullstack/stack/referrals	Tracked in the request proxy, 60/20 split.
Testing	vitest	`vitest run` in CI. `node --test` for small CLIs, `bun test` on Bun repos, Playwright for browser flows.
Lint + format	Prettier + ESLint	Biome or Oxlint where a repo already uses it. Do not add a second formatter to a repo.
CI	GitHub Actions	ci.yml, codeql.yml and threatcrush-scan.yml on every repo. Release after merge with gh release; a merged PR reaches nobody until the release is cut.
AI	c0mpute via @profullstack/ai-providers, MCP via @modelcontextprotocol/sdk	Every text or JSON model call goes through @profullstack/ai-providers: c0mpute peer nodes first, OpenAI and Anthropic only as alternating fallbacks. One Infernet trusted-client key (ifc_) per app as C0MPUTE_API_KEY. Never import openai or @anthropic-ai/sdk directly for text. Anything an agent should operate ships an MCP bridge.
Promotion	myna (mynaposter.com)	The last phase of every ship: socials, both blogs and a CrawlProof ad from one command. Syndicated copies carry rel=canonical back to our page.
Data	NicheDB, RSS Amplifier, r4ck	Datasets come from and go back to nichedb.dev. Feeds are submitted through @profullstack/submit-feed. OpenProfile.md for people, /.well-known/openaccess.json for access terms.

Combos

Different stacks for different reasons. Each one names live products built on it.

Web app

web-app

The default for a new product. Next 16 renders the UI, a Hono app mounted inside it serves the API, Turso holds the data, and one Railway service runs web and worker together.

Use it when

You are starting a product that has a UI and a database.
The data fits SQLite semantics: one writer, modest joins, no Postgres extensions.
You want one service, one deploy, one domain.

Notes

Next inlines process.env.NAME at build time, so read runtime secrets through a non-literal key.
A 200 on /api/health proves nothing about the worker. Check the logs for its up line after a deploy.

Built on it

rssamplifier.com p0dcasters c0upons opensourcelegends.com sorrycheck sinkstate bufferoverride nightcell7

Concern	Choice	Notes
Framework	Next 16, React 19	App Router. proxy.ts, not middleware.ts. Server components by default.
API	Hono inside Next	Mounted under /api. Versioned routes live at /api/v1/... and OAuth callbacks at /api/v1/<provider>/<function>/<endpoint>.
Database	Turso (libSQL) via @libsql/client	Forward-only SQL migrations in packages/db, or Drizzle with dialect turso. Migrations must be safe to run twice concurrently.
UI	Tailwind 4 + shadcn/ui	Scoped behind a ui.css without preflight when adding to an existing site. Plain CSS modules on marketing sites.
Realtime	Server-Sent Events	WebSockets only for chat, terminals and multiplayer.
Background work	A worker process in the same container	Supervised by the entrypoint; the container exits non-zero when either process dies. BullMQ on Redis only when the queue is the product.
Storage	Railway volume or Cloudflare R2	R2 buckets private, served through signed or proxied routes.
Layout	apps/web, packages/db, services/worker	Root-only vitest config, tsconfig.base.json with strict flags. Copy nightcell7 or reeleel rather than inventing a layout.

Web app on Postgres

web-app-postgres

The previous generation of the same shape, and still the largest by count. Next 16 on Supabase, or on a self-hosted Postgres in the same Railway project. Kept where the data needs Postgres or the app already lives there.

Use it when

The app is already on Supabase or Postgres. Stay there.
You need row-level security, pgvector, heavy relational joins, or a queue on Redis next to the database.
Several services share one database and the write volume is real.

Notes

Do not move an app to Turso as part of a feature. Classify it first: easy Turso, needs Postgres, or consolidate.
coinpayportal is public with 19 forks. Never put real data in a fixture there.

Built on it

coinpayportal.com ugig.net crawlproof.com marksyncr.com logicsrc.com w3bs.org brisk.news icemap.app

Concern	Choice	Notes
Framework	Next 16, React 19	Same conventions as web-app.
Database	Supabase Postgres, or self-hosted Postgres on Railway	Supabase client via @profullstack/stack/supabase. New Postgres apps self-host on Railway (w3bs.org is the reference). Index every foreign key you will cascade through.
Auth	Magic link + passkeys on the app's own users table	Supabase Auth exists in older apps; the local users.id is always the primary key.
Queues	BullMQ on Redis	Custom job ids must not contain a colon.
Migrations	supabase/migrations or plain SQL	Applied in CI or on boot, never by hand in the dashboard.

API service

api-service

Hono on Turso with no framework in front of it. For pollers, crawlers, data APIs, MCP servers and anything whose UI is a few server-rendered pages or none at all. Bun or Node, chosen per repo and pinned.

Use it when

The product is an API, a feed, a dataset or a daemon.
The UI is small enough to render from Hono (JSX or templates) or lives in a separate app.
You want the smallest possible service: one process, one SQLite file or one Turso database.

Notes

Bun-only gotchas: Bun.serve idleTimeout kills long streams, and Bun's SQL client stringifies arrays. Keep those behind small adapters.

Built on it

nichedb.dev r4ck.dev genrewatch.com tipoffwatch.com watchnews.now agenticjobs tronbrowser.dev reeleel

Concern	Choice	Notes
Framework	Hono 4	Web-standard Request/Response. Same app runs on Bun and Node; the router is the only Hono-specific code.
Runtime	Bun or Node, pinned	Bun for stream-heavy or IO-heavy services (genrewatch, tipoffwatch, niche-db, r4ck). Node + pnpm when the service shares code with a Next app or a CLI.
Database	Turso (libSQL)	Embedded replica or remote. FTS5 for search, with the raw query escaped; libSQL cannot bind undefined.
Rate limiting	@profullstack/throttle	Credentialed callers get 600/min, anonymous 100/min, over the limit is a 402 with an offer.
Agent surface	MCP bridge in the CLI package	One query vocabulary across page, API, CLI and MCP.
Deploy	Railway, Dockerfile or Nixpacks	railway.json with healthcheckPath. Pin pnpm 10 on Nixpacks; corepack cannot launch pnpm 11.

CLI and TUI

cli-tui

Terminal tools for people and agents. Node and TypeScript, commander for arguments, hqtui for anything with a screen, an MCP bridge so an agent can drive the same commands, published to npm under @profullstack.

Use it when

The user is a developer, an operator or an agent.
The tool wraps a site or API we run (nichedb, rssamplifier, coinpay, r4ck, readm3).
You need a dashboard in a terminal rather than a browser.

Built on it

@profullstack/hqtui @profullstack/nichedb @profullstack/coinpay @profullstack/readm3 @profullstack/g1tz @profullstack/r3q @profullstack/billing cli-tools

Concern	Choice	Notes
Runtime	Node 20+ (Bun optional)	Node is required: CLIs run in GitHub Actions and on customer machines. Bun is fine for development.
Arguments	commander	Subcommands map one to one onto MCP tools.
TUI	@profullstack/hqtui	btop-grade dashboards, one import. A mouse must work: one click unfolds, hover highlights.
Config	~/.<tool>.json + @profullstack/synconfig	Allowlisted snapshot synced with the tool's cloud.
Install	npm i -g @profullstack/<tool> and curl \| sh	The installer does the whole job. Never document a manual follow-up step.
Testing	node --test or vitest	bun test on Bun repos; mock.module is process-wide there.
Release	GitHub release workflow publishes to npm	Bump before testing. A brand-new scoped package 404s for minutes after publish.

Desktop

desktop

Electron, with the product's CLI bundled inside the app. A desktop install gives the CLI too, with no system Node, and the two surfaces cannot disagree because they are the same build.

Use it when

The product needs a tray, a window, the filesystem or OS input.
A CLI already exists and the desktop app is a second surface for it.

Built on it

mynaposter diskpush threatcrush pairux.com nixampmedia2markdownr4ck.dev

Concern	Choice	Notes
Shell	Electron	Tauri was tried and retired.
Inside	Hono or Next, same as the web surface	The renderer is the web app; the main process hosts the API locally.
CLI	Bundled via extraResources	The installer writes a shim: ELECTRON_RUN_AS_NODE=1 exec app resources/cli/dist/bin.js. Build the bundle with pnpm deploy --prod --legacy.
Native modules	N-API only	Electron's ABI differs from system Node. @libsql/* passes; anything with V8 symbols does not.
Distribution	GitHub releases + curl installer	Headless machines get a CLI-only tarball. Homebrew, apt, rpm, scoop and nix repos exist for pairux.
Auto-update	From GitHub releases	Set the tool's NO_AUTO_UPDATE env when testing a dev binary.

Games

games

Babylon in the browser, with every gameplay rule in a package that cannot import a renderer. The same rules run in the client, in the authoritative match server and in tests, so a rule exists exactly once.

Use it when

The product is a real-time 3D scene the player acts inside, not a page they read.
It has to run in a browser first, with the desktop build as a second surface rather than the only one.

Notes

Distant point lights and glows are camera-facing sprites held at a fixed screen size, never scaled geometry. A 25 mm firefly is sub-pixel past 30 m and no amount of scaling the mesh fixes that.
Budget the shell download. Models ship geometry, UVs and a named material slot; the engine binds the real textures by that name so one atlas is not shipped ten times.

Built on it

nightcell7 nightcell7.com

Concern	Choice	Notes
Renderer	Babylon.js	WebGPU where the browser has it, WebGL2 fallback. The fallback is a supported path, not a degraded one.
Physics	Havok via @babylonjs/havok	Only where real collision response is needed; most props are static.
Rules	A pure game-core package	No Babylon, no DOM, no Electron imports. This is the rule that makes a client and a server able to agree.
UI	Preact, outside the frame loop	The component layer never owns a per-frame transform. HUD readouts are text-node writes behind a change check, not a render pass.
Multiplayer	Server-authoritative over WSS	The client sends input intent. The server owns movement validation, damage, death, respawn and score. Shared messages live in their own protocol package.
Build	Vite + vite-plugin-pwa	Set registerType and actually wire the update prompt; prompt with no handler means returning players never get a new build.
API and data	Hono, Drizzle, Postgres	Same as api-service. Never cache /api, matchmaking or tickets in the service worker.
Desktop	Electron	The desktop combo applies unchanged; the renderer is the same web build.
Art	Generated by committed Blender scripts	No asset without provenance. One Blender metre is one game metre, GLB with glTF-compatible PBR, COL_ colliders and SOCKET_ attachment points.

Mobile

mobile

Expo and React Native, as apps/mobile inside the product monorepo. It shares the API client and packages with the web app rather than living in its own repo.

Use it when

The product needs to be in the app stores or on a phone home screen with native capabilities.
A PWA is not enough (push, background, camera, payments in-app).

Notes

Start with the PWA. Most products never need this combo.

Built on it

threatcrush pairux.com postammo.com reeleel tronbrowser.dev

Concern	Choice	Notes
Framework	Expo (React Native)	React 19. Shares types and the API client with apps/web.
Layout	apps/mobile in the product monorepo	Standalone *-mobile repos are the old pattern and are dormant.
Backend	The product's own api-service or web-app	No separate mobile backend.
Store release	sh1pt	One codebase to every store, registry and channel.

Library

library

Code that two or more products need becomes a @profullstack/* package. Runtime-neutral core, subpath exports, one npm package per concern, released from GitHub.

Use it when

You are about to copy a module from one repo into another.
A site needs a component another site already ships (player, leaderboard, feed submission, contact-form guard).

Built on it

@profullstack/stack @profullstack/x402-gateway @profullstack/throttle @profullstack/player @profullstack/modern-css @profullstack/leaderboard @profullstack/form-guard @profullstack/submit-feed

Concern	Choice	Notes
Shape	ESM, TypeScript, subpath exports	`@profullstack/stack/referrals`, `/email`, `/supabase`, `/feedback`, `/coinpay`, `/crawlproof` is the pattern. Peer-depend on next, react and clients rather than bundling them.
Core	Web-standard APIs	fetch, Request, Response, URL, crypto.subtle, ReadableStream. Runtime-specific code behind an adapter. A /core entry must never import a node: module.
Build	tsup or plain tsc	Node type-stripping needs .ts specifiers; pair with rewriteRelativeImportExtensions so dist still emits .js.
Tests	vitest	Contract tests where the package defines a protocol (x402, submit-feed, OpenProfile).
Release	Bump, merge, gh release	A release workflow publishes. Ship pkg@latest in docs, never update -g. pnpm 11 refuses packages younger than a day unless excluded from minimumReleaseAge.

Systems

systems

Rust when the product is a single static binary that has to be fast (benchmarks, transports, agents on servers). Go when the upstream ecosystem is Go. Python only for security tooling that lives in that world.

Use it when

A JavaScript runtime would be the bottleneck or the dependency you cannot ship.
The upstream you build on is in that language (LiveKit for agentbbs, nmap and Kali tooling).

Built on it

c0mpute agentbbs fiche-agentic vu1nz.com kali

Concern	Choice	Notes
Rust	tokio, axum, clap, reqwest	c0mpute is the reference. Auto-update from GitHub releases on first run.
Go	Standard library + the upstream SDK	agentbbs pins livekit server-sdk-go and protocol together.
Python	Managed by mise, venv per project	Security tooling and GitHub Actions only (vu1nz).
Distribution	GitHub releases, curl installer, homebrew tap	Same installer rule: it does the whole job.

House rules

The conventions an agent has to follow on any Profullstack repo, whichever combo it is on.

Ship it, never stop at in progress

An agent does not end its turn on "still running, I will report when it lands". Work handed to a subagent, CI or a deploy is driven to merged, released and verified live in the same turn, then reported once with the result. Stop early only for a real blocker a person must clear: a login, or a decision that is theirs.

Every site takes payment from launch

Launching a site includes taking crypto: npx @profullstack/coinpay-onboard site <name> --webhook <public url> makes its CoinPay business, copies the payout wallets in, sets the webhook and writes the COINPAY_* keys into the site vault. Idempotent; every step must print a check before the launch is announced.

Launch on a Moshpit name

New products launch on a Moshpit name (pit.moshcode.sh), not a new ICANN domain, served from our own box with a registry-signed certificate and listed on the Moshpit ring. Announcements give the <name>.pit.world address for browsers without Moshpit DNS.

Reuse the house package first

Before adding a dependency or writing a component, grep the repo for @profullstack/ and check npm. The package usually exists and is often already installed.

Secrets live in the vault

Set production secrets on the Railway service and record them in the logicsrc team vault. Never write one into a .env in the repo, and never ask a person to.

Auth is magic link plus passkeys

The link proves the address and the address is the account. Passwords are optional and only for devices that cannot do either.

Signup asks for the profile

Every signup collects email, first_name, last_name, company_domain, job_title and linkedin_url through @profullstack/profile, in that order. Email and name are required; the other three are optional. The company is filled from a work email.

Every API offers webhooks

An app with an API and accounts lets customers register webhook endpoints for its events through @profullstack/webhooks: the /api/v1/webhooks routes, a CLI command and MCP tools over them, and emit() wherever something happens. Never hand-roll signing or retries; apps on their own scheme move to it, sending their old header alongside until receivers switch.

User keys are sealed by the user

Any key, token or password a user gives an app (exchange and wallet keys, BYO AI keys, OAuth tokens, SMTP passwords) is sealed with @profullstack/sealed-secrets under a passphrase the user holds, with a one-time recovery key. No server key, env var or database dump can open it. Servers write new secrets through the seal inbox; workers use them only inside an UnlockStore session the user opened. The Settings "Key vault" card, its browser code and the /my/vault routes come from the same package (vault-card, vault-ui/auto, vault-server); never hand-roll one. Operator secrets stay in the logicsrc team vault.

Installers do the whole job

If a feature needs a component, the installer or update command installs it. No documented manual follow-up step. DNS routing is the one thing that stays explicit.

Push to the default branch deploys

PRs are merged, not parked. Release after merge. Then announce through myna, with rel=canonical on every syndicated copy.

Our domains only

Add the custom domain before writing any URL down. Never publish a *.up.railway.app address.

Migrations run twice

Web and worker both migrate on boot. Ledger writes are insert-or-ignore and every migration is safe to apply concurrently.

Large catalogues use a sitemap index

/sitemap.xml is an index; entities are chunked by month of creation so past files never change.

OAuth callbacks are namespaced

/api/v1/<provider>/<function>/<endpoint>, using whatever API prefix the project already has.

Every product is a customer of another

Wire products together when the integration is load-bearing: x402 settles through CoinPay, blogs open CrawlProof ads, myna distributes every ship, NicheDB sells the data.

Copy has no LLM tells

Short sentences, no em dashes, no rule-of-three flourishes. This applies to posts, READMEs and announcements.

A wedged process restarts without a person

Every container gets a HEALTHCHECK that hits its own /healthz, so a blocked event loop shows as unhealthy. watchdog-autoheal restarts what Docker marks unhealthy, three times an hour at most, then emails. In-process, watchDependencies exits when the shared DB or Redis client stops answering.

Agents get a first-class surface

A site ships its data as Markdown or JSON at a stable URL, a CLI ships an MCP bridge, and training crawlers pay through x402 rather than being blocked.

Not in the stack

Things an agent might reach for by habit. Do not.

Hetzner: Ruled out permanently. Railway hosts the fleet; a netcup box and DigitalOcean droplets cover what needs a VM.
Vercel, Fly.io, Cloudflare Workers: Not deploy targets. One repo has a fly.toml and none have a wrangler config. Railway is the host.
Supabase for a new app: Turso is the default. Supabase and Postgres stay where they already are.
.env files as the source of secrets: The vault and the platform env are the authority. A file is a stale copy.
Password-first auth, next-auth: Magic link plus passkeys. @profullstack/auth-system is password-only and is the exception, not the pattern.
SvelteKit, Primate + SurrealDB, Express for new work: Earlier generations still in maintenance. Do not start anything new on them.
Tauri: Retired in favour of Electron with the bundled CLI.
mocha, jest, Prisma: vitest and plain SQL or Drizzle.
Oxc, Oxlint, Oxfmt, Rolldown as a default: On the roadmap since June and present in six repos. Use the repo's existing lint and format setup until parity is proven.
Hand-rolled players, rate limiters, contact-form guards, feed forms: Each of these is a published package already.
video.js, plyr, a bare hls.js or mpegts.js: @profullstack/player wraps hls.js and mpegts.js already. video.js 10 ships no player at all: it throws VJS8_LEGACY_* on v8 code.
*.up.railway.app URLs: Our domains only.

Runs in production

Every Profullstack product is built on this stack. The full list, with install commands, lives in the docs.

Browse every product

Maintainers

One senior engineer, a fleet of agents, and every change through review, tests and CI.

Anthony Ettinger

Founder, Profullstack, Inc.

GitHub LinkedIn

riotcoder

The agent persona that writes most of the code.

OpenProfile OpenAgent

Want this stack on your product?

We build new products on it and move teams off per-project backends.

Book a call

The open source stack for the agentic era

Every surface

Agent native

Proven in production

Open and portable

The libraries

Build

Stack

HQ TUI

Orgs

Bridges

libSQL PG

Player

Form Guard

Browser Fingerprint

Submit Feed

Scraper Daemon

Agents

MCP Server

NicheDB

media2md

OpenProfile

Profile

Agentic Jobs

Proxy

Money

CoinPay

x402 Gateway

x402 Client

Throttle

Keys

Referrals

Affiliates

Redeem Credits

Ship + operate

sh1pt

ThreatCrush

CrawlProof

Watchdog

Encrypt

Emailer

Every package

Start with a prompt

The blueprint

Pick a combo

Shared defaults

Combos

Web app

Use it when

Notes

Built on it

Web app on Postgres

Use it when

Notes

Built on it

API service

Use it when

Notes

Built on it

CLI and TUI

Use it when

Built on it

Desktop

Use it when

Built on it

Games

Use it when

Notes

Built on it

Mobile

Use it when

Notes

Built on it

Library

Use it when

Built on it

Systems

Use it when

Built on it

House rules