Architecture & Technical Approach
How Waypoint builds automation systems—local-first AI, SQLite storage, Cloudflare edge delivery, and human approval gates on every external action.
- Local-first AI keeps data on hardware you control
- SQLite is the single source of truth for every record
- Cloudflare edge delivers the client portal and public site
- Make.com orchestrates integrations with your existing tools
- Human approval gates on every email, SMS, payment, and deletion
- Audit logging captures who approved what and when
- You own the system, the database, and the documentation
- Client-supplied text is untrusted data—never an authorization
- Approval is enforced in code, not by prompting the model
- Credentials come from environment variables, never hardcoded
- External communication requires an approval record
- Node ESM runtime—no framework, no build step
- SQLite via better-sqlite3 for durable local storage
- Local Ollama models for chat and planning
- Cloudflare for edge delivery and TLS termination
- Make.com for workflow integration and API orchestration
- Vanilla JS front end—no React, no webpack, no bundler
How the pieces fit together
A request enters through the Cloudflare edge, which terminates TLS and routes to the Node server. The server reads and writes to a local SQLite database—the single source of truth for clients, leads, missions, and approval records. Local Ollama models handle chat and planning without sending data to a third-party API. When a workflow needs to touch an external system—your CRM, your email provider, your SMS gateway—Make.com orchestrates the integration, and every outbound action passes through an approval gate before it is allowed to execute.
Make.com connects your automation to the tools you already use: Google Sheets, your CRM, your email platform, your calendar, and more. We build the scenarios, document the mappings, and hand them over. You can inspect every step and modify them without proprietary dependencies.
AI models run on local hardware through Ollama, so your data never leaves your environment for inference. Cloud fallback exists for edge cases, but the happy path is local. This keeps latency low, costs predictable, and sensitive conversations private.
A single SQLite file holds every record—clients, leads, tasks, approvals, audit logs. It is portable, durable, and easy to back up. No separate database server to maintain, no connection pooling to tune, no surprise cloud database bill.
Cloudflare handles TLS, caching, and edge delivery for the public site and client portal. This puts your content close to visitors without exposing your local database to the internet. The edge proxies to the Node server, which remains the only thing that touches SQLite.
Before any email sends, any SMS goes out, any payment is captured, or any record is deleted, the system creates an approval record and waits. A human reviews the proposed action and approves or rejects it. The model cannot skip this step—the policy layer blocks execution until approval exists.
Every approval, every rejection, every automated action, and every manual override is written to the audit log with a timestamp and the actor responsible. You can reconstruct what happened, when, and who authorized it—at any time, without asking us.
Security boundaries
Every piece of text that comes from a client—an intake form, a website, a document—is treated as untrusted data. It can inform a decision, but it can never authorize one. A submitted form cannot trigger a payment or send an email on its own.
The policy layer classifies every action as automatic, approval-required, or blocked. This classification lives in code, not in a prompt. A model that tries to send an email without an approval record gets a hard error, not a polite reminder.
API keys, tokens, and passwords come from environment variables managed on your hardware. They are never hardcoded, never logged, and never echoed in error messages. Rotating a credential is a config change, not a code change.
If an action reaches outside the local system—email, SMS, payment, CRM update, integration change—it requires an approval record first. There is no background process that quietly sends on your behalf. Everything is visible and accountable.
What you own
When Waypoint delivers an automation system, you receive the running system, the SQLite database file, the Make.com scenarios, the documentation, and the code. Nothing is held back behind a retainer. If you stop working with us tomorrow, your automation keeps running, your data stays accessible, and your documentation tells you how every piece works. That is what client ownership means in practice—not a promise, but a deliverable.
Book Free AuditRead our security approach