Back the first deployable release.
Support the engineering, testing, packaging, security, and deployment work required to move from a working prototype to a release founding supporters can help bring into the world.
Back the Build →CAMPAIGN + PROOF PORTAL
Websites need
a presence.
ORB Weaver is a living, embodied website host and consultant. It understands the compiled Site World, stays aware of the visitor’s context, explains what matters, points with its Ping Light, and acts only with permission.
WORKING NOW prototype foundationClaims labeled by status
SITE WORLD GROUNDED
PING LIGHT GUIDANCE
ACTIONS PERMISSIONED
PRESENT · AWARE · EMBODIED
THE PRODUCT POSITION
Not a floating chat widget.
The website, embodied.
ORB Weaver is the interface between the visitor and the website. It knows pages, routes, sections, controls, forms, products, services, documents, and relationships—while maintaining awareness of the current route, viewport, scroll position, and available controls.
PASSIVE CHAT WIDGET
×Detached from the site
×Waits for typed questions
×Generic responses
×Leaves the visitor to navigate
EMBODIED WEBSITE PRESENCE
✓Understands the Site World
✓Speaks and explains in context
✓Points with the Ping Light
✓Requests permission and verifies actions
THREE DISTINCT PATHS
Choose how you want
to help build it.
This portal keeps public campaign support, hands-on beta participation, and private investment conversations clearly separated.
Test it on real websites.
Apply to exercise the Site World, explanations, Ping Light navigation, permissions, browser actions, and owner controls in real operating conditions.
Join the Founding Beta →Review the commercial case.
Explore the market problem, architecture, moat, deployment model, business model, roadmap, capital requirement, and strategic partnership opportunity.
View the Investor Brief →WORKING-PROOF MODEL
Presence changes the
website experience.
01Visitor asks→
02ORB understands intent→
03Identifies the correct page or control→
04Explains it→
05Points to it→
06Requests permission where required→
07Performs or verifies the action
This sequence defines the product’s end-to-end proof target. Individual capabilities are labeled below according to their current state.
CAPABILITY LEDGER
No blurred claims.
No invented proof.
Every capability belongs to a declared state. The campaign funds the work required to turn the active prototype foundation into a stable, deployable product.
Embodied browser presence
A visible ORB experience, website-aware conversation, dashboard integration, and functional account access exist in the current prototype.
Compiled Site World
Grounding across pages, routes, sections, controls, forms, products, services, documents, and their relationships.
Guided website action
Route and viewport awareness, Ping Light pointing, permission requests, verified browser actions, deployment packaging, and beta hardening.
Deeper embodiment
Advanced spatial presentation, guided tours, local DockStation support, and optional cloud synchronization.
FOR KICKSTARTER BACKERS
Fund a defined release,
not an undefined idea.
The campaign release is a deployable Website ORB foundation with grounded Site World understanding, contextual guidance, permissioned browser actions, owner controls, and a documented installation path.
Deployable runtime, Site World compiler, Ping Light guidance, permission controls, verified action flow, memory controls, installation documentation, and founding beta release.
Founder runway, implementation engineering, hosted model validation, GPU testing, security, infrastructure, deployment packaging, documentation, and production testing.
A milestone-based schedule will be published with the Kickstarter campaign after scope and funding tiers are finalized. Progress will be reported against deliverables, not invented dates.
Founding supporter recognition, development updates, early demonstrations, beta consideration, and release access will be defined before campaign launch. No unapproved tier or price is claimed here.
Browser variance, model latency, voice reliability, security, permissions, packaging, and deployment complexity. Scope will be controlled around a fast, verifiable first release.
Build transparently, demonstrate only real capability, protect permission boundaries, report setbacks honestly, and keep the first release focused on useful website presence.
FOUNDING BETA APPLICATION
Real websites.
Serious participation.
The beta is for website owners, operators, agencies, and technical collaborators willing to test an emerging embodied interface and provide structured feedback.
What you will test
Site World compilation, grounded explanations, visitor context, Ping Light guidance, permission prompts, browser-action verification, and owner-facing controls.
Expected participation
Install on an approved test site, complete guided scenarios, document failures clearly, join periodic feedback sessions, and avoid presenting beta behavior as finished capability.
Spaces and privacy
Founding beta capacity will be limited by support and testing resources. Test scope, data handling, retention, access, and removal expectations will be documented before participation.
Founding-user benefit
Early influence over usability, deployment, explanations, controls, and documentation—plus recognition as a founding beta contributor if desired.
FOUNDER
Built from conviction,
proven through work.
Bryan Spruk created ORB Weaver after years of building AI systems and studying how people actually encounter technology. He saw that websites kept adding passive chat boxes while leaving visitors to understand the site, find the right control, and finish the task alone.
ORB Weaver is his answer: a knowledgeable, embodied website presence that understands its environment, communicates clearly, guides attention, respects permission, and remains accountable for what it does. The goal is not to imitate a person. It is to give the website an intelligent host.
Explore the primary ORB Weaver website ↗THE CAMPAIGN GOAL
The prototype is working.
Help us build the first deployable release.
Back the public build, apply to test the release, or review the private commercial briefing. Each path has a different role—and every contribution moves toward the same proof.