Getting Started with SeekBytes
From initial configuration to generating your first operational manual. Learn how our Skill 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: Plan Your Deployment
Depending on your security and compliance requirements, you can deploy SeekBytes in three different environments. Each option provides full access to our Skill Engine and Verification API (Agent Proof). Use the interactive planner below to choose footprint, engine packages, ship format, and authentication—then submit your plan so our team can follow up.
Plan which engines you need, where they run, how they ship, and how your side authenticates—built for today’s packages and the engines coming next.
Engines can be split later—start with the footprint that matches security and residency.
Pick the engine packages that match your deployment. Mix freely across categories.
Core platform engines
Intelligence & verification
Capture, vision & physical world
Same engines, different delivery units—pick every format your sites will use.
Credential types are independent of where engines run. Pick types, then setup methods.
Your engine deployment plan
A forward-looking package map—not tied to a single monolith. Use it for procurement, security review, and phased rollout.
Footprint
Ship formats
Engine packages
Authentication
Your email is used only as a point of contact so our team can follow up on this plan.
Step 2: Know Your Organisational 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 Skill Engine is the "brain" of the platform. It doesn't store your raw digital media permanently; it processes it in real-time through your configured Connectors.
- Ingestion: The Engine pulls digital media (recordings, PDFs, screenshots, or related documentation) 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 (Skill Engine) = Operational Knowledge (Knowledge Base).