reBe Presence

Add Presence to your website

Give visitors cited answers from material you publish. Their questions stay in their browser. Your website remains usable even when their device cannot run a local model.

Choose what fits

Free$0

One website, cited public answers, local-only visitor memory.

Publish$19 / month

Up to ten connected websites with the same governed install.

Read the terms · Read the privacy policy

Prove your website

Add the one-time code to the loader line or publish the DNS record shown below. No local ports, keys or internal tools are involved.

No proof created yet.

Describe what your site may answer

Everything entered here is published for visitors. Do not paste private material.

Install once

Generic site: paste the exact loader shown after configuration before the closing </body> tag.

Configure a verified site to get its exact loader.

WordPress: install the signed reBe Presence package, enable it, and use the same owner proof code when asked.

WordPress install guide

Owner health

Create or restore this owner session to see configuration, publication, activation and health.

Exact publication identities
No publication yet.

Plan and lifecycle

Free · no paid subscription

One active website is included.

Cancellation takes effect at the paid period boundary. Already delivered public artifacts remain immutable. Releasing a website reverses its ownership claim and stops its active bootstrap.

Browser and device limits

The website loads first. Published Corpus answers do not require a model. Local reasoning requires WebGPU, enough device memory and the visitor's explicit Connect choice. There is no hidden cloud-model fallback.

Connected history and model downloads live only in that browser profile. Clearing or losing it removes them; reBe cannot restore them from a server. Visitors can reset their local Presence data from the panel.

Your owner access on this device

The key controls configuration. It is never placed in a URL or export. If you forget it, this browser stops controlling the site; domain proof remains the recovery boundary.