Enterprise direction
Enterprise work focuses on organization-level control.
We are defining organizational controls, governance, managed deployment, and support around the open Peekling browser engine.
01 · STATUS
A managed path for teams with many sites.
We're exploring how larger teams could govern Peekling across many sites while preserving the character's gentle presence and the browser runtime's safety model. The open-source browser runtime is available now for teams that own their integration and deployment.
02 · AVAILABLE NOW
Teams can deploy the browser runtime today.
The current release can be pinned to an exact version, served from a CDN or self-hosted, and integrated directly into a page. The host application owns its product logic, deployment policy, and user relationship.
- Character Packs stay data-only through strict validation.
- The runtime stays telemetry-free and host-controlled.
- Hosts apply their own CSP, CORS, integrity, and release policy.
- Reduced motion, dismissal, cleanup, and failure containment belong to the browser contract.
03 · FUTURE CAPABILITIES
Enterprise work starts with the controls teams actually need.
- Administration
- Organization policy, roles, identity integration, and a clear place to manage deployments.
- Managed delivery
- Deployment hosting, rollout rings, authenticated updates, and recovery controls.
- Privacy-aware measurement
- Explicit measurement choices shaped around consent, data ownership, and the runtime's telemetry-free foundation.
- Optional service integrations
- Clearly bounded service contracts for teams whose use cases require managed processing or organization workflows.
- Commercial support
- Procurement materials, support paths, ownership boundaries, and service commitments designed around real team requirements.
04 · EVALUATION CHECKLIST
Evaluate the open-source path available today.
The browser runtime fits teams that can own integration, deployment, and updates. Use this checklist to connect the current release to your team's requirements and identify ideas for future enterprise work.
- Confirm that a browser-only, host-owned integration fits the use case.
- Review character artwork, attribution, and redistribution rights separately from the engine license.
- Test CSP, CORS, reduced motion, dismissal, keyboard use, and cleanup in the real host page.
- Pin versions and assign ownership for updates, incident response, and rollback.
- Record each desired managed capability and share the most important use case on GitHub.
05 · FUTURE BOUNDARY
Future enterprise work will preserve user control.
This direction builds on pack validation, page ownership, dismissal, reduced motion, privacy, and the runtime's data-only boundary. Team feedback will help define the right contract and the right time to build it.