The operating layer for intelligence.
Operveil is a standalone operational-intelligence platform. It brings workspaces, people, capability packs, connections, settings and oversight into one place. Each workspace owns its context and authority.
Operational intelligence. Human control.
Your operation.
One clearer mind.
Meet Ghost, your digital manager inside Operveil. Connect the systems you use, understand what needs attention and coordinate the next move—with evidence, memory and boundaries.
For owners, managers and teams. A scoped rollout, not unrestricted autopilot.
GHOST INTELLIGENCE CORE
Connected contextA signal, not just a notification.
Understand. Recommend.
Act within your authority.
Product illustration · not live workspace data
Connected, not entangledContext that lastsPermissions before actionsOutcomes, not promises
A platform. An intelligence. Your operation.
Operveil connects the pieces.
Ghost sees the bigger picture.
A digital manager, not another inbox.
Ghost is the intelligence inside that platform. It turns authorized signals into an understanding of your operation, keeps useful context, coordinates work and checks the outcome. It should tell you what it knows, what it does not know and why a next step matters.
Operveil is not DramAudit POS. DramAudit remains an independent hospitality operating system, with separate login, data and billing. Ghost can read permitted DramAudit information through a scoped, revocable connector; it does not inherit POS authority.
Intelligence with a follow-through
From a signal
to a verified outcome.
A good digital manager does more than answer a question. Ghost is built around a seven-step cycle that keeps context, coordination and accountability together.
Seven capability packs
Give your Ghost
the right responsibilities.
Start with the work that matters to you. Packs organize capability and commercial scope. They never replace membership, permissions, approvals or the connected source an action needs.
ManagerYour daily operating picture
Bring the day's priorities, open questions and next steps into a concise management view.
- Context-aware questions and briefings
- Priorities, tasks and approval requests
- Continuity across conversations and handoffs
Scoped rollout · requires workspace identity and authorized sources.
OperationsCatch the exception. Close the loop.
Connect operational signals to incidents, follow-up and outcome checks instead of leaving them as disconnected alerts.
- Incident review and correction recommendations
- Operational checks and escalation paths
- Proactive initiatives and outcome tracking
Built/tested components · execution adapters are not enabled.
FinanceKnow what the numbers actually say
Review venue-specific sales, payment mix, tips and financial exceptions with traceable sources—not invented certainty.
- Daily sales briefings and PDF report workflow
- Payment, product and employee breakdowns where supplied
- Missing-data and reconciliation flags
Report pilot · source completeness varies; automatic dispatch stays off.
StaffingPeople, coverage and follow-through
Use permitted workforce context to understand coverage and prepare staffing recommendations.
- Workforce and coverage context
- Staffing suggestions with explicit assumptions
- Task ownership and escalation to a manager
Requires workforce connection · schedule publication is not enabled.
InventoryUnderstand stock before the surprise
Connect stock signals, usage and product relationships to a clearer inventory review.
- Stock and usage observations from connected records
- Shortage and discrepancy recommendations
- Reviewable tasks, not silent purchasing or adjustments
Requires inventory source · purchasing and stock writes are not enabled.
ExecutiveA clearer view across your responsibilities
Turn the context you are entitled to see into focused owner briefings, trends and decisions.
- Evidence-backed management summaries
- Priorities and unanswered questions
- Workspace-specific oversight and audit history
Scoped rollout · access to one workspace never grants access to another.
VisionVisual context, with a privacy boundary
Add a time-bounded visual observation when a configured camera source and permitted use genuinely require it.
- On-demand camera or clip review
- Source, time and uncertainty attached to observations
- Channel, retention, privacy and approval controls
Configuration-gated · no blanket surveillance, face identification or unrestricted camera access.
Pack billing and provider checkout are still in test-stage development. Production self-service purchase is not released. Request a scoped walkthrough and quote.
Many systems. Explicit connections.
Reach across your operation.
Never reach beyond permission.
A connector specifies the workspace, source and allowed actions. Ghost Bridge is the governed link to enrolled edge devices. A connection being present is never permission to execute.
DramAudit / POSFiles & knowledgeEnrolled devicesWhatsAppEmail · Calendar · AccountingCameras / DVR
SCOPED · VERSIONED · REVOCABLEConnector registry
+ Ghost BridgeIdentity · grants · audit
+ Ghost BridgeIdentity · grants · audit
GhostYour isolated workspaceDramAudit
Venue-specific operational reads and report workflows. Celtic and Nevizade remain separate contexts. Source completeness and exact permission decide what is available.
Bridge & computer agents
Signed enrollment, certificate lifecycle, replay protection and bounded observations. Current Ghost/Fleet integration is device-status read-only. Installing software or controlling a desktop is not enabled in Ghost.
A verified communication identity maps to a person, membership, role and active workspace. One number can serve several workspaces; a message's wording cannot select tenant authority. Live switching and automatic report delivery remain disabled.
Files & knowledge sources
Bring permitted source material into structured context, with provenance, freshness and confidence. A file is information, not an instruction to expand Ghost's authority.
Business tools & APIs
Email, calendar, accounting and custom APIs fit the connector model. Each needs its own adapter, credential-vault reference, scope and validation. These are not universal plug-and-play integrations today.
Camera & DVR context
Visual observations require the Vision pack, authorized channels, privacy configuration and a verified provider/device path. Available cameras do not grant continuous monitoring or model-training consent.
Context that does not disappear
Know what is true.
Remember what matters.
Ghost's World State is a structured view of an operation—not a claim to know everything. Long-term memory gives useful context a place to live, without letting old assumptions become new facts.
World State
Observations retain their source, timestamp, freshness and confidence. Missing, stale, conflicting or partial information remains visible.
Structured memory
Workspace-specific history, decisions and reviewable context support continuity. Memory and authority stay separate; remembering an approval does not grant a new one.
Proactive follow-through
Initiatives can turn a permitted signal into a recommendation, task or escalation. Outcome verification records what actually happened instead of trusting a confident response.
WORLD STATEIllustrative record
An observation has a history.
- Source
- Authorized venue connector
- Observed at
- Venue-local time + UTC timestamp
- Freshness
- Fresh / stale / unknown
- Confidence
- Evidence quality, not certainty
- Boundary
- This workspace. This grant.
A better question is often the next action.
Control is part of the product
A powerful assistant.
A deliberate boundary.
Ghost is a digital manager—not an unrestricted digital owner. You define the workspace, connections, responsibilities and review requirements. The system must enforce those limits on the server.
Identity before context
Verified person → workspace membership → role → capability grants → active context. Tenant authority is never inferred from a business name in free text.
Approval before impact
High-impact work needs configured authority, an appropriate approval and an enabled adapter. A subscription, remembered preference or connected integration cannot bypass that boundary.
Secrets stay separate
Connector credentials use protected vault references. Sensitive settings, bounded access and workspace isolation are architectural requirements—not data to paste into a chat.
A trail you can follow
Audit records, signed Bridge requests, replay protection, idempotency and unknown-result reconciliation make actions reviewable. Stop controls must take precedence over automation.
Your data is not blanket consent
Customer messages, employee records, files and camera observations do not automatically authorize training or fine-tuning. Training consent and provider data governance are separate decisions.
Settings that can evolve
Workspace settings cover model/provider preferences, language and connected context where supported. Expanded owner controls are in tested source code and await rollout; no setting grants new authority.
These are product boundaries, not a certification claim. Some enforcement components are built and tested but not installed in the current pilot. See availability below.
Less noise. More useful next moves.
What a better day could look like.
Illustrative scenarios—not live automation promises. Every flow depends on the correct pack, source, authority and rollout.
A closeout you can actually read.
Review a venue-local daily PDF with sales, payments, products and staff/tip breakdowns when the source provides them. Missing data is flagged rather than replaced with zero. Delivery history distinguishes a generated report from a delivered message.
A clear briefing, with the evidence beside it.An exception with a next step.
A connected signal suggests a coverage or operational issue. Ghost explains the evidence, prepares a reviewable follow-up and brings it to the right person. It does not silently publish a schedule or change a staff record.
An owner, a task and a verification step.A stock question before a shortage.
Compare permitted inventory observations with usage context. Ghost can surface a discrepancy and recommend a count or review. Ordering, stock adjustments and recipe changes remain separate, explicitly authorized actions.
A reasoned recommendation, not a surprise purchase.Know exactly where things stand
The vision is broad.
The rollout is explicit.
Operveil and Ghost are in a scoped pilot. Implementation, testing, live verification and release are different milestones. A feature description here is not a claim that every connection is already active.
Workspace access & local coordination
Secure workspace login, local tasks, settings, audit views and walkthrough requests. Managed Ghost read surfaces depend on explicit workspace grants.
Expanded Ghost intelligence & governance
Source code covers structured memory, source sync, model settings, approvals, identity/enrollment, entitlement gates and Bridge lifecycle. The running pilot does not yet contain all of those revisions.
Reports, WhatsApp & device/provider paths
Venue report workflows exist, but full source/report acceptance remains partial. Automatic daily WhatsApp sending is off pending the exact pilot migration and signed gateway end-to-end validation. Cameras and provider billing require their own setup and evidence.
Unrestricted computer control & autonomous writes
Ghost currently reads permitted Fleet device status. Privileged installation, desktop control, payments, purchases and schedule publication are not enabled Ghost actions. Production self-service pack checkout is not released.
Marketing availability reviewed: October 2, 2026. Workspace setup and current evidence take precedence.
Start with a responsibility, not a blank prompt
Build your Ghost around your work.
- 01
Define your workspace
Choose the operation, people, roles and language. Keep unrelated businesses separate.
- 02
Choose the scope
Pick the capability packs and a concrete first outcome. Confirm availability and a scoped quote.
- 03
Connect deliberately
Authorize exact sources and enroll approved devices. Review data access, privacy and approvals.
- 04
Verify, then expand
Validate a real workflow, its evidence and its boundaries before enabling more responsibility.
The important questions
Clear answers.
No mysterious superpowers.
Is Ghost just a chatbot?
Conversation is one interface. The product model also includes connected observations, World State, structured memory, tasks, approvals, audit and outcome checks. Availability depends on your workspace's verified rollout—not everything is live today.
Can it run my entire computer?
Not today through Ghost. The current Fleet connection is read-only device status. Future computer actions need an enrolled agent, a typed action, current permission, approval where required and a verified execution result. Installing an agent must never imply blanket control.
Can I use Operveil without DramAudit?
Yes, Operveil is a separate product and workspace boundary. DramAudit is an optional connector, not its identity provider or shared database. Other sources need supported adapters and scoped setup; this is not a claim that every vendor is already integrated.
How does one WhatsApp number handle several businesses?
The identity path is verified sender → person → membership → role → grants → active workspace. Short-lived pairing codes are for initial linking only. Naming a venue in a message cannot authorize access. The production live switch stays off until signed gateway and pilot migration validation are complete.
Does buying a pack let Ghost execute actions?
No. Commercial entitlement and operational authority are separate. Observe, read, recommend, ask, create-task and execute are distinct permissions. High-impact actions also need configured approval and an enabled, tested adapter.
What happens when the data is incomplete?
Ghost should preserve missing, stale, partial and unknown states, with provenance and confidence. It must not invent source records or call an unknown outcome successful. Financial report acceptance is still partial; review the underlying evidence before relying on a total.
Is my data used to train models?
Connected access is not blanket permission for training or fine-tuning. Training consent, retention, privacy and each model provider's data terms must be configured separately. Outcome memory in your workspace is not the same thing as training a model.
Can I change models, language or connections later?
The product includes workspace configuration and source-tested owner model/provider settings. Expanded controls await rollout. This website supports English, French and Turkish; that does not imply every product module supports every language. Changes never broaden authority implicitly.
Your next move, made clearer
Meet the Ghost
your operation needs.
Bring one real workflow. We'll map the sources, responsibilities, limits and evidence needed for a useful first rollout.
Request a walkthrough Already have a workspace? Log inNo credentials or payment details needed for an inquiry.
Website inquiry & privacy notice
The walkthrough form collects your name, organization, contact details, optional message and follow-up consent. It is stored in Operveil's inquiry system and audit history so the team can respond. The server also uses request/IP timing for abuse prevention. Do not include passwords, API keys, payment-card data or sensitive employee/customer records. No advertising or analytics tracker is included in this marketing page. For inquiry access, correction or deletion requests, contact info@dramaudit.com. Operational workspace/provider privacy and retention arrangements must be reviewed separately before connecting data.
Contact about your inquiry data ↗