Frequently Asked Questions
Straight answers, in writing — how fast you go live, how security works, what it costs, and who owns what.
Straight answers, in writing — how fast you go live, how security works, what it costs, and who owns what.
Not websites — infrastructure. Every client gets the Araptus Engine: a website (Highlander), a firewall (Gateway), operations (Doon), knowledge (Cortex), insight (Signal), security monitoring (Sentinel), and local discovery (Directory), running as one machine on your own isolated stack. Subscribe to the engines you need.
One engineer — Kris Black, 22+ years in software. No sales team, no project managers, no rotating support queue. The person who built every engine is the person who answers when you call.
The engine configures per industry: home services, insurance, retail and e-commerce, agencies, technology, travel, nonprofits, healthcare, and real estate all run on the same infrastructure with industry-specific modules. See Industries for your vertical.
Email info@araptus.com, call 281-846-4097, or book a call. You talk to the engineer on the first call — there's nobody else to route you through.
Under six minutes from the first sitting. Highlander assembles your site from 150+ components, deploys to managed infrastructure, and connects your domain in the first hour of working together. Content work is underway by minute fifteen; by week two the whole ecosystem is dialed in.
Everything runs on a shared board — you see what's in progress, what's next, and what shipped. You get one hour a month of live collaboration, plus a feedback pipeline built into your site so requests land directly in the queue.
Your industry and your goals. If you have an existing site, its content can be scraped and rebuilt; if you're starting fresh, content gets written as part of the build. Either way, launch doesn't wait on a content phase.
Yes — sites get rebuilt on Highlander with every old URL 301-redirected, so rankings carry over instead of resetting. A short dip during re-crawl is normal; recovered sites typically settle higher than they started because the architecture is faster and cleaner.
Astro and TypeScript on Vercel for the frontend, Rust for the backend engines, per-client Hono gateways for security. No jQuery, no PHP, no plugin runtime shipped to your visitors — the stack is the reason the speed and security numbers hold.
90+ PageSpeed is the floor, not the goal — it's what the architecture emits on day one. Core Web Vitals inside thresholds (LCP under 2.5s, CLS under 0.1), GTmetrix A grades. Static-first output means there's nothing heavy to tune out later.
Mobile-first, not mobile-adapted. Every component in the library is built for phones first and scales up, and every build is tested across devices before it ships.
Yes — WordPress, Contentful, and Strapi for content; Shopify, WooCommerce, and Medusa for e-commerce; GA4, email platforms, and booking systems — all through one integration layer. Change platforms later without rebuilding the site.
Fifteen languages through proper i18n architecture serving pre-translated content — not a translation plugin that mangles copy and breaks SEO.
That's built in. The AI Context Layer regenerates machine-readable files describing your business on every deploy — so when ChatGPT, Perplexity, or Claude answer a question in your industry, you're the citable source.
As a pipeline, not a product: every request passes the Gateway's 12-layer proxy, security middleware runs inside the code, and every deploy is HMAC-signed — unsigned builds don't go live. The record: zero breaches across 60+ deployments.
Rate limits, honeypot traps, and scanner detection trip the wire; the threat is blocked and logged, and an alert fires to Slack, Discord, or any webhook. You hear about it after it's handled — that's the point of having it built in.
Yes. Per-client isolated infrastructure — your own database, your own API keys, no shared hosting — is exactly the architecture regulated industries need, and we build healthcare deployments with compliance requirements designed in from the start.
Monitored 24/7 — Sentinel watches every deployment, and site health, search console, and deploy status are tracked continuously. Backups are standard, and your content lives in version-controlled markdown, which is its own recovery layer.
Every build is quoted for your business — the engine configures per industry and per scope, so there's no one-size price list. Quotes are detailed and transparent, with no hidden costs. The catalog shows everything the ecosystem offers.
No contracts. You subscribe to the engines you need and stop when you want. The work keeps you, not the paperwork.
You do — completely. Your content is plain markdown you can read, diff, and take anywhere; your data lives in your own instance and is queryable and exportable. If we ever part ways, you leave with everything. That's the point.
Still have questions?
Let's TalkDiscover new experience of web development.
The exact folder structure and workflows I use to run a 40+ client agency from an Obsidian vault. No plugins. No SaaS. Just markdown.
How I manage 60+ client ecosystems from Warp terminal and Claude Code — no project management UIs, just custom tooling that ships.
Skip LangGraph and CrewAI. Claude Code with folders and markdown files is the most powerful AI tool. Here's how we build ecosystems with it.
Nate B. Jones' 2026 AI predictions shape how I retool clients with Highlander — AI training, hallucination detection, and authentic branding.
Get started with enterprise-grade development solutions.