SignalCost Beacon

Plug in local AI control for every office.

Beacon helps your business understand what AI is being used for, stop requests that should not run, choose the right approved AI service, and keep sensitive checks inside your office by default.

SignalCost Beacon product preview
SignalCost Beacon

The small office device that helps you manage employee AI use before it turns into cost, risk, or customer-data exposure.

Reserve Beacon when you want simple local AI controls for an office, branch, or customer site without asking employees to change how they work.

Offices that want AI controls close to employees.
Business owners and MSPs that need simple rollout across many locations.
Teams that want sensitive prompt checks handled inside their own environment.
How It Works

Local control in the office, managed from SignalCost.

Both versions answer the same business questions: who is using AI, what work it supports, whether it should be allowed, where it should run, what it costs, and what proof should be kept.

01

Activation-code setup

Power on the Beacon, log in to SignalCost, and enter the activation code shown by the unit. SignalCost ties that device to the right company and office.

02

Capture source catalog

Beacon exposes the same capture source choices as Cloud: native browser capture, endpoint, SDK, MCP, OpenTelemetry, and local Beacon capture. Install the source that matches the traffic your team already uses.

03

Local AI request check

Beacon can review the request in the office first, decide whether it fits company rules, and only then allow approved AI use.

04

Provider coverage states

Beacon turns local evidence into detected, observed, and connected provider states. Network enforcement is available as an optional advanced control after capture is working.

05

Managed from SignalCost

SignalCost shows which offices are active, which policies are installed, whether updates are current, and whether the local dashboard is healthy.

Capture coverage

Discovery comes first. Credentials are optional.

Every provider moves through a clear state so teams know what SignalCost can prove now and what an integration would add later.

Detected provider

Discovered automatically from captured traffic.

No credentials required.

Observed provider

Usage, source, employee, model, and estimated cost are visible.

Enough evidence to report.

Connected integration

Optional credentials are added for billing, routing, or enrichment.

Account access stays separate.

Manual setup is a secondary action.

Choose Add billing or routing integration only when the workspace needs invoices, exact account reconciliation, provider routing, model catalogs, or enrichment.

See provider coverage
THE NEXT MOVE

Turn the first captured signal into operating value.

Once the first provider record appears, move from evidence to action without reworking the shared capture layer. Start small, then expand with proof.

01

Capture the work

Download the native browser installer, activate Beacon One, or connect an endpoint, SDK, MCP, or OTel source.

02

Authorize the economics

Connect captured activity to a workflow, budget, provider, model, policy, and agent wallet before spend compounds.

03

Prove the result

Reconcile usage, review the AI general-ledger dimensions, and measure the outcome before expanding to more packs or locations.

Customer Concerns

Straight answers for owners, finance, security, and operations.

Does the box replace Cloud?

No. Beacon is the office device. SignalCost Cloud still manages your account, policies, reports, billing, support, and device list.

What happens if connectivity drops?

Beacon keeps the latest approved rules locally and follows the fallback choice your company sets: keep running, stop risky requests, or stay local-only.

How hard is installation?

Beacon is designed so a small office can start without a custom IT project: plug it in, enter the activation code, start local capture, and install the native browser or managed source that fits the office. Add provider credentials later only when billing or routing requires them.

Do we need network enforcement?

No. Capture and provider discovery work without a proxy, browser certificate, or router change. Add optional router, DNS, inline, or proxy enforcement only when the company needs direct-provider bypass controls.

Keep prompt-sensitive work local

Beacon can make the sensitive decision inside the office while SignalCost receives the business record needed for reporting and audit.

Avoid a heavy technical rollout

Beacon detects the local router, DNS, and Beacon address so offices get a clear recommended path instead of a custom networking project.

Scale by site or MSP customer

Add devices by office, branch, or customer while keeping each site’s rules, reports, and evidence separate.

What You Get

SignalCost Beacon uses the same SignalCost decision model.

Cloud and Beacon are different ways to deploy the product. Provider coverage, capture sources, rules, costs, approvals, reports, and audit records stay consistent.

Included capabilities

  • Device identity, activation-code enrollment, and company/site binding.
  • Native browser capture installer and managed source catalog for endpoint, SDK, MCP, and OpenTelemetry adapters.
  • Local dashboard for activation, capture coverage, provider evidence, live traffic, health, settings, support, updates, and test decisions.
  • Local rule checks with optional SignalCost classifier help when more confidence is useful.
  • Admin-visible prompts by default, with content-minimized Private Proof records available for workflows that require stricter privacy.
  • Optional network enforcement for offices that need router, DNS, inline, or proxy bypass controls.
  • 90-day local traffic history by default, with Cloud Archive available for longer audit and reporting needs.
  • Daily update checks, support bundle, rollback, and company-controlled fallback modes.

Best-fit adoption path

  • Small-office hardware unit in a SignalCost enclosure.
  • Connects to the local office network and the SignalCost account assigned to that office.
  • Rules and reporting managed in SignalCost with local enforcement options.
  • Capture sources are installed from one catalog and bind to the company workspace without provider credentials.
  • Designed for offices, branches, MSP customer sites, and teams that want AI control without a heavy technical rollout.
Choose your starting point

Start with 30 days free. Add Beacon One when a device or office needs local control.

Start as an individual with personal protection or as a team with token-bundle pricing. Beacon One remains the local-control device for people and locations that need AI activity reviewed near the source.