Launch allowances are documented limits—not “free forever” claims.See verified limits →
Independent systems practice
Plan my system

CONTROLLED DEMONSTRATIONS

Try the capabilities SITEBORNE can build into a client-owned web system.

Every demonstration runs from transparent seeded inputs. Responses are labeled, deterministic, and require no paid credential, secret, or live provider.

Simulated response

AnswerMap

Ask a question about seeded SITEBORNE content. The response cites only the local demonstration source.

Launch allowance
10,000 neurons/day; model availability varies and some models require Workers Paid.
Upgrade trigger
Neuron use reaches 75%, selected model moves to paid, or quality requirements exceed available models.
Fallback
Semantic retrieval, source excerpts, conventional search, and contact escalation.
Last verified
2026-08-01
How this works

The demo uses seeded SITEBORNE content and deterministic browser logic. Production mode would use a server-side adapter, usage metering, source restrictions, timeouts, and a kill switch.

What happens when it fails

The module enters a public fallback state. Conventional search, page navigation, or direct contact remains available.

Review the full module architecture

Simulated response

IntentPath

Use deterministic choices to route to a service or preparation path.

Launch allowance
100,000 Worker requests per day; static asset requests should bypass Worker execution.
Upgrade trigger
Dynamic requests approach 70% of the daily allocation or CPU limits constrain execution.
Fallback
Static decision tree, service links, and conventional project brief.
Last verified
2026-08-01
How this works

The demo uses seeded SITEBORNE content and deterministic browser logic. Production mode would use a server-side adapter, usage metering, source restrictions, timeouts, and a kill switch.

What happens when it fails

The module enters a public fallback state. Conventional search, page navigation, or direct contact remains available.

Review the full module architecture

Simulated response

LeadBrief

Turn an inquiry into a structured, non-scoring internal brief.

Launch allowance
3,000 emails/month, 100/day, one custom domain, one webhook endpoint, 30-day retention.
Upgrade trigger
Daily or monthly volume approaches 75%, longer retention is needed, or multiple domains are required.
Fallback
Deterministic extraction from structured fields plus the original inquiry.
Last verified
2026-08-01
How this works

The demo uses seeded SITEBORNE content and deterministic browser logic. Production mode would use a server-side adapter, usage metering, source restrictions, timeouts, and a kill switch.

What happens when it fails

The module enters a public fallback state. Conventional search, page navigation, or direct contact remains available.

Review the full module architecture

Simulated response

SiteSentinel

Run a simulated critical-path verification with explicit failure states.

Launch allowance
3,000 emails/month, 100/day, one custom domain, one webhook endpoint, 30-day retention.
Upgrade trigger
Daily or monthly volume approaches 75%, longer retention is needed, or multiple domains are required.
Fallback
HTTP checks, static assertions, and manual QA checklist.
Last verified
2026-08-01
How this works

The demo uses seeded SITEBORNE content and deterministic browser logic. Production mode would use a server-side adapter, usage metering, source restrictions, timeouts, and a kill switch.

What happens when it fails

The module enters a public fallback state. Conventional search, page navigation, or direct contact remains available.

Review the full module architecture

Critical checks: homepage, project brief, confirmation path, metadata, and expected CTA.

Simulated response

ResourceMatch

Rank seeded resources by requirement fit, not affiliate compensation.

Launch allowance
30M queried vector dimensions/month and 5M stored vector dimensions.
Upgrade trigger
Dimension use, corpus size, latency, or quality requires a paid vector store.
Fallback
Typed filters and visible comparison table.
Last verified
2026-08-01
How this works

The demo uses seeded SITEBORNE content and deterministic browser logic. Production mode would use a server-side adapter, usage metering, source restrictions, timeouts, and a kill switch.

What happens when it fails

The module enters a public fallback state. Conventional search, page navigation, or direct contact remains available.

Review the full module architecture