Getting Started with SeekBytes
From initial configuration to generating your first operational manual. Learn how our Video Processor Engine integrates with your organizational boundary.
Welcome to SeekBytes. Our platform is designed to turn your team's actual work into governed, reusable operational knowledge. To get started, you need to understand two core pillars: Deployment (where the engine runs) and Configuration (how your data is structured).
Step 1: Choose Your Deployment Option
Depending on your security and compliance requirements, you can deploy SeekBytes in three different environments. Each option provides full access to our Video Processor Engine and Verification API (Agent Proof).
Cloud (SaaS)
Immediate access. Managed by SeekBytes. Perfect for teams wanting to start capturing knowledge in minutes without infra overhead.
Private Cloud (VPC)
Deployed within your own AWS/Azure/GCP environment. Keeps data processing within your network perimeter while staying cloud-native.
On-Premise
For high-security environments. Run the entire SeekBytes stack on your own physical or virtualized hardware behind air-gapped firewalls.
Step 2: Configure Your Organizational Structure
Once your environment is ready, the setup flows through three levels of configuration. This ensures that each user's data remains isolated and governed.
Tenant
Your organizational boundary. This is where your users, billing, and global security policies live.
Project
A dedicated workspace for a specific team or domain (e.g., "IT Ops" or "Finance Compliance").
Connectors
The bridges to your data. Configure storage buckets or system APIs to let the Engine ingest evidence.
How the Engine Connects to Your Data
The Video Processor Engine is the "brain" of the platform. It doesn't store your raw videos permanently; it processes them in real-time through your configured Connectors.
- Ingestion: The Engine pulls a recording from your secure storage (S3, Azure Blob, etc.) via a Connector.
- Processing: It extracts "Episodes" (frames, metadata, UI text) within your Tenant boundary.
- Crystallization: The processed output is stored in your Knowledge Base, becoming a reusable Skill.
Pro Tip: Most users start with the Cloud deployment to configure their first Tenant and Connector, then transition to VPC or On-Premise as their compliance requirements evolve.
Transitioning to the Knowledge Base
The end goal of "Getting Started" is to populate your Knowledge Base. Every successful run of the Engine creates a verified link between raw operational evidence and governed documentation.
Once your Tenant is configured and your first Connector is active, you are ready to explore the Knowledge Base and start managing your Enterprise Intelligence Moat.
Summary
Configuration (Tenant + Connectors) + Engine (Video Processor) = Operational Knowledge (Knowledge Base).