Vision Analytics · Data Engineering · AI · IoT

Data and AI,
built to run anywhere.

Fluxor Software builds data and AI infrastructure — cloud-native or fully offline, your choice. Sightlinq, PyEdge, and SchemaShifts came out of solving real problems for real clients across vision, edge, and distributed data — then were productized for anyone to use, at any size, in any industry.

9+
Database Engines · SchemaShifts
<40ms
Edge Latency · PyEdge
0.894
mAP50 · Sightlinq
3+
Cloud AI Backends · Bedrock, Vertex, Azure OpenAI

What We Do

Vision Analytics· Data Engineering· AI· IoT

Built for Edge Hardware, Cloud Platforms & Distributed Databases

Not Built In A Vacuum

Every Product Started
as a Client Engagement.

Sightlinq, PyEdge, and SchemaShifts weren't built speculatively and then pitched to customers. Each one solved a real problem for a real client first — in vision analytics, edge IoT, and distributed database governance — and was productized once the pattern proved out. That's still how Fluxor works: from large enterprises to single-site small businesses, what gets built for one client's hardest problem often becomes the next product anyone can use.

Deployment Philosophy

Cloud-Native or Offline.
Never Both by Default.

Fluxor doesn't force one deployment model. Every product plugs into the AI and cloud stack you already run, or runs with zero cloud dependency at all — same platform, your choice.

☁️
Cloud-Native

Plug Into What You Already Run

Sightlinq connects to AWS Bedrock, Google Vertex AI, and Azure OpenAI for model backends, and to Azure Blob, S3, or GCS for storage. SchemaShifts governs your database wherever it's hosted. Multi-site and hybrid deployments are a config change, not a re-architecture.

AWS BedrockGoogle Vertex AIAzure OpenAIS3 / Blob / GCS
🔒
● Fully Offline

Or Zero Cloud Dependency

Air-gapped, factory LAN, or remote site with no reliable connectivity — every product runs fully on your own infrastructure with no cloud account, no per-event metering, and no external calls required.

air-gappedon-premisezero depsno cloud account

What We Build

Four Independent Products.
One Data & AI Philosophy.

Each product stands on its own — different buyer, different problem, no requirement to use the others. Any company, any size, any industry: from a Fortune 50 enterprise to a single-site small business.

🎯
● Production Ready

Sightlinq

End-to-end visual AI training — capture, annotate with AI assistance, train on your own GPU/CPU or a cloud backend (Bedrock, Vertex AI, Azure OpenAI), and deploy back to the edge. Any industry with a camera and a detection problem, not just manufacturing.

Real results — PCB defect detection
0.894
mAP50 best class
83 min
CPU-only training
on-prem or cloud AIauto-label loopGPU or CPUedge deploy
Full Sightlinq overview
● Production Ready

PyEdge

Edge stream processing for anyone with sensor or event data and a rule to run against it — no vision required. SQL-style rules, a REST API, and a role-based dashboard, with zero dependencies beyond the standard library.

on-premisezero depsSQL rulesREST API + dashboardMQTT & HTTP
Full PyEdge overview
🗄️
Production Ready

SchemaShifts

Schema governance for distributed databases — versioned migrations, immutable audit logs, and distributed locking across Cassandra, Spanner, DynamoDB, CockroachDB, and more. For any company running a distributed database, vision or AI use case not required.

cassachangespanchangecockroachchangedynamochange
Visit SchemaShifts.com
🔧
Custom Engineering

Fluxor Engineering

When the answer needs to be custom, not a platform: bespoke vision analytics systems from cloud pipelines to privacy-first on-sensor inference, plus AI infrastructure — self-hosted LLM serving (vLLM), RAG, and MCP integration for teams who want AI without renting someone else's API.

custom vision analyticsvLLM / self-hosted AIRAGMCP
How we approach custom builds

Fluxor Engineering

Custom Systems.
Engineered for the Problem.

When the answer isn't a platform, it's a bespoke build. Vision AI systems across retail, logistics, agriculture, safety, and beyond — cloud or edge, image-retaining or privacy-first. And AI infrastructure: self-hosted LLM serving with vLLM, RAG, and MCP integration for teams who want AI on their own terms. Same philosophy, two engineering tracks.

🔬
Any Architecture, Any Deployment
Cloud-hosted, on-premise, edge device, or on-sensor — the deployment model follows the problem. A retail analytics system and a privacy-sensitive occupancy counter have different requirements. We build for both.
🌐
Real Problems Across Real Domains
Quality inspection, crop monitoring, footfall analysis, safety compliance, wildlife tracking. Vision AI is useful far beyond the factory floor — we build systems that reflect that breadth.
🛡️
Privacy by Design — Where It Matters
When the use case calls for it, on-sensor inference means pixel data is discarded before a frame ever exists. A hardware guarantee, not a policy promise. When it doesn't — the image stays, and we help you handle it responsibly.
Privacy by Design → Discuss a Project
fluxor-vision · pcb_defect_test_v1 · live inference
38
ms / frame
0.894
mAP50
3
Defects
AI INSIGHT · Sightlinq on-premise
Before Export & Train: Reviewing 240 annotations from last session
Sightlinq: Quality score: 8.2/10. 3 issues — Image 47: box too wide, includes non-defective area. Image 91: label should be mouse_bite not open_circuit. Image 188: defect visible but unannotated. Correcting before training improves model accuracy.
# pcb_defect_test_v1 · edge inference · 640px DETECT missing_hole conf=0.894 bbox=[112,84,156,128]
DETECT spur conf=0.761 bbox=[304,210,340,248]
DETECT mouse_bite conf=0.703 bbox=[488,62,531,98]
WARN spurious_copper conf=0.48 bbox=[200,310,244,350] below_threshold
OUTPUT → { defects: 3, classes: ["missing_hole","spur","mouse_bite"], board_id: "PCB-0047", pass: false, latency_ms: 38 }

Sightlinq — How It Works

Seven Steps.
One Click at a Time.

Every step after image capture is automated. The only human action is annotation — and by Round 4, even that is mostly reviewing what the model already got right.

01
Edge
Image Capture
Uploader agents watch configured folders on edge devices. Content-hash deduplication — the same image is never synced twice, from any device.
automatedhash dedupscheduled
02
Ingest
Task Creation
New images trigger automatic task creation and assignment. Annotators open their app to find work already waiting — no manual handoff.
automatedRBAC-aware
03
Annotate
Human Review — or AI-Assisted
Round 1: every box drawn by hand. Round 2+: the trained model pre-draws boxes and annotators correct only mistakes. Images and video both supported — CVAT interpolates boxes between frames automatically.
manual → AI-assistedimages + videointerpolation
04
Export
Annotation → Training Format
Click Export & Train. Sightlinq converts annotations, splits 80/15/5 train/val/test automatically, and writes the manifest to storage.
automated80/15/5 split
05
Train
Model Training — Your Hardware
Training starts immediately on your machine. GPU if available, CPU otherwise. Live status in the browser; close the tab and it keeps running. Notification on completion.
GPU or CPUlive statusno cloud
06
Deploy
Auto-Deploy as Live Inference
Best model deployed automatically as a live serverless inference function. The annotation UI can now use it to pre-label the next batch without any configuration.
serverlessautomatedONNX / TensorRT / TFLite
07
Loop
Continuous Improvement
Next batch arrives. Model pre-annotates. Annotators spot-check edge cases. Accuracy improves every round without reconfiguring anything.
self-improvingdomain-specific
Annotation time — per 500-image batch
Round 1
8–10 hrs
Round 2
3–4 hrs
Round 3
1–2 hrs
Round 4
30 min
Round 5+
minutes

Real test — PCB defect detection
0.894
mAP50 best class
27
Auto-detections
693
Training images
83 min
CPU-only training

No GPU required. Intel i7-1355U laptop, 30 epochs, 83 minutes. The missing_hole class reached mAP50 0.894 — production-quality for inline inspection on commodity hardware.

Full Sightlinq Overview →

Privacy by Design

The Camera That
Never Saw a Thing.

Most camera-based AI systems treat privacy as a policy — a promise made in a document, honoured until a breach, a misconfiguration, or a subpoena. Fluxor Vision treats privacy as an architecture. The guarantee holds regardless of what happens downstream.

That said, not every deployment should discard the image. Quality inspection needs the frame. Security forensics depends on it. Audit trails sometimes require visual evidence. We support both approaches — traditional image pipelines and on-sensor inference — and help you choose the architecture that fits your context, with a clear view of what each carries with it.

Signal chain diagram: Traditional Camera AI versus Fluxor Vision on-sensor inference

Two architectures, two different sets of trade-offs. Fluxor Vision supports both — the right choice depends on what your deployment actually needs.

Traditional Vision Pipeline — Image-Centric
📷
Sensor captures frame
Full resolution image created on chip
Image exists
💾
Frame buffered / stored
Edge device, NVR, or local storage retains footage
Retained
🧠
Model runs against image
Industrial PC, Raspberry Pi, or embedded GPU — the model processes a stored frame
Full frame
📊
Result + image available
Inference output and source image both accessible
Retained
When this is the right choice: Quality inspection review, security forensics, audit evidence, model retraining, defect traceability — any workflow where a human may need to verify what the model saw. Everything runs on-premise, within a secure perimeter, with no internet required. Image retention is a feature here — manage it with a clear policy, defined retention windows, and access controls.
Privacy-First Pipeline — On-Sensor Inference
🔬
Sensor + model on same chip
Inference executes inside the imaging sensor itself
On-sensor
🧹
Pixel data discarded
No image buffer, no frame ever formed or stored
No image
📤
Structured output only
Counts, coordinates, classifications — edge-local, no cloud
Metadata
Application receives result
No image ever leaves the device. No internet required.
Private
When this is the right choice: Occupancy sensing, people counting, presence detection, safety monitoring — any context where the insight matters but a visual record of who was there does not, or where retention would be disproportionate, unwelcome, or legally complex. Also runs fully within a secure perimeter, with no cloud dependency.

Image retention makes sense here

🔍
Quality Inspection
Defect images feed retraining pipelines and provide traceability for production audits. The frame is the evidence.
🦌
Wildlife Camera Traps
On-sensor detection triggers the camera — storing only species-confirmed frames rather than hours of blank footage.
🌿
Agricultural Monitoring
Disease and pest images feed agronomic review. Images are of crops, not people — retention carries low privacy risk.
🏪
Smart Retail Checkout
Product images support dispute resolution. Frames are of items, not faces — a proportionate retention decision.
🚗
Vehicle Forensics
Wrong-way entry or incident investigation may need the frame. On-sensor triggers capture; policy governs retention.

Structured output is sufficient here

🚶
Person Presence Detection
A boolean — occupied or not — is all an access system, HVAC controller, or lighting trigger needs. No image adds value.
🔢
People Counting
Footfall is a number. Queue length is a number. Neither requires knowing who the people were.
🧍
Fall and Posture Detection
An alert that someone has fallen is what matters. The image of how they fell creates a disproportionate record.
🦺
PPE Compliance
An event log of compliance status is actionable. A video archive of every worker who forgot their vest is a liability.
Gesture Control
A gesture command is a user action. An image of the hand that performed it is an unnecessary biometric record.
🅿️
Parking Occupancy
Available or not available. That is the entire output a parking display needs. No registration plate image required.
📦
Parcel Detection
Present, moved, or removed — three states. A tamper alert doesn't need continuous surveillance footage to be useful.
🚦
Traffic Flow Analysis
Vehicle counts, dwell times, and incursion alerts are policy inputs. No video stream is needed to derive them.

⚖️ Data Minimisation — Article 5(1)(c)

GDPR requires that personal data be adequate, relevant, and limited to what is necessary for the stated purpose. On-sensor inference is a direct technical implementation of this principle — if the purpose is to count occupants, producing a count satisfies the purpose. Producing a video archive does not.

Both pipelines apply.Image-retaining systems should define the minimum retention window that satisfies their purpose and delete beyond it.

🏗️ Hardware Guarantee vs Policy Promise

A data protection policy states what an organisation intends to do with data. A hardware guarantee defines what the system is architecturally incapable of doing. When pixel data is discarded on-sensor, no policy violation, misconfiguration, breach, or legal compulsion can produce footage that was never created.

Privacy-first pipeline.The guarantee holds across breach, insider threat, and compelled disclosure. Policy-based approaches carry residual risk under each of these.

📋 Is Inference Output Personal Data?

A count of persons in a room is unlikely to constitute personal data. A precise skeletal keypoint sequence associated with a named individual may. The output format and combination of signals determines exposure — not the hardware alone. Seek legal review for any inference model whose output could identify or profile individuals.

Context-dependent.On-sensor architecture removes the question for the raw image layer. What the structured output carries is a separate legal assessment.

📝 Responsible Deployment — Both Approaches

Regardless of pipeline choice, responsible deployment includes: a Data Protection Impact Assessment scoped to the context; clearly defined retention windows for any stored data; transparency signage where individuals may be present; and a legal review of inference outputs against applicable data protection law.

Our commitment.We provide DPIA guidance, configuration review, and deployment documentation as part of every engagement — not as an afterthought.

Full Capability Map

15 Deployments.
Right-Sized for Each Context.

Every capability below is available across both pipeline approaches. The badge indicates the natural fit — but every deployment is a considered decision, not a default.

● Privacy-first fit ● Image-retaining fit ● Context-dependent
🚶
Person Presence Detection
Occupancy, access control, or environmental triggers. The result is a state — present or not — and that state is all any downstream system requires.
🔢
People Counting
Footfall, queue depth, crowd density — delivered as integers over time. Actionable at the aggregate level with no individual-level record.
🛒
Retail Shelf Monitoring
Empty slot detection and planogram compliance. Privacy-first for customer-facing spaces; image capture appropriate for back-of-house where no individuals are present.
🦺
PPE Compliance
Real-time detection of missing protective equipment. Structured output suits compliance event logging; image capture is appropriate where incident investigation requires visual evidence.
🧍
Posture and Fall Detection
Pose estimation detects falls, prolonged stillness, or unsafe posture. An alert is the outcome — not a recording of the individual in distress.
🔍
Quality Inspection
Surface defects, assembly errors, missing components. Defect images feed retraining and provide audit traceability — image retention is a production requirement, not a risk.
🚗
Vehicle Detection and Classification
Counts, classifications, and directional flow on-sensor. Incident investigation may justify image capture on a triggered basis — routine monitoring does not.
🦌
Wildlife Camera Traps
On-sensor detection triggers targeted image capture — only when the right species appears. Eliminates weeks of blank storage and runs on battery power indefinitely.
🌿
Agricultural Monitoring
Crop disease, pest damage, ripeness classification. Images of plants carry no privacy implication — retain freely, review agronomically, retrain seasonally.
🏪
Smart Retail Checkout
Product identification by shape and appearance. Item images suit dispute resolution; face or person images do not belong in a checkout pipeline.
Gesture Control
Hand keypoint detection drives touchless interfaces. A command event is the entire output — no biometric trace, no image record, no session log.
🏋️
Fitness Rep Counting
Pose keypoints count reps and flag form deviations in real time. Performance data belongs to the user — not to a server storing their workout footage.
🅿️
Parking Space Occupancy
One sensor, multiple bays, one output per space. Live signage updated from occupancy events. No registration plate image, no video feed, no retention obligation.
📦
Package and Parcel Detection
Delivery, movement, and tamper detection by inference event. Image capture on tamper trigger is a proportionate choice; continuous surveillance of a doorstep is not.
🚦
Traffic Flow Analysis
Vehicle type counts, junction dwell times, wrong-turn detection — all derivable from on-sensor classification. No video stream is needed to produce any of these outputs.

Responsible deployment — whichever approach you choose

Every Fluxor Vision engagement includes a configuration review against your stated use case, guidance on Data Protection Impact Assessments, retention policy recommendations, transparency signage requirements where individuals may be present, and a frank conversation about whether image capture is justified by the deployment context — or whether structured output is sufficient. We do not have a default answer. We have a process for arriving at the right one.

SchemaShifts + Vision AI

Sightlinq Detects.
SchemaShifts Governs What Comes Next.

Sightlinq stores every detection — structured, local, completely customer-owned. Customers who want to go further — vector search across millions of inspections, RAG-grounded AI tooling, MCP integration — need a database built for it. Six of the nine databases SchemaShifts governs support native vector search. SchemaShifts handles every schema change that vision data requires as the detection model evolves.

How SchemaShifts extends Sightlinq data
🎯
Sightlinq
Trains · Detects · Stores
customer adopts a SchemaShifts-governed database ↓
📋
SchemaShifts
Governs schema · versioned migrations · immutable audit log
detection events + embeddings + vector indexes ↓
🗄️
Vector-Capable Database
Cassandra · Spanner · CockroachDB · SingleStore · YugabyteDB · TiDB
ANN search · MCP · customer-built RAG ↓
🧠
RAG + MCP — customer-built
Evidence-grounded answers from full inspection history
  Customer-controlled  ·    Schema governed  ·    Audit trail included

From detection events to searchable institutional memory.

Sightlinq stores every detection — that is exactly what it is designed to do. Customers who want to build vector search, RAG, or MCP tooling on top of that data need a governed database that supports it. That is the role SchemaShifts plays.

Six of the nine databases SchemaShifts governs support native vector search. When a customer adopts one — Cassandra 5 for air-gapped production lines, Spanner for global multi-site deployments, SingleStore for sub-millisecond HTAP — SchemaShifts governs every schema change: VECTOR column additions, ANN index creation, embedding dimension upgrades. Immutable audit log included.

Sightlinq does not change. The customer's chosen database gains the governance layer it needs to support vector search, RAG, and MCP as the detection model evolves and new defect classes are added.

Full Technical Deep-Dive
Vector-capable databases — governed by SchemaShifts
Apache Cassandra 5
Native Vector · ANN

VECTOR column type + SAI ANN-OF queries + HNSW indexing. Billions of detection events stored alongside embeddings — no joins, no separate store. Best fit for air-gapped, high-throughput production lines.

Google Spanner
10B+ Vectors · ScaNN

GA vector search to 10B+ vectors via ScaNN. SQL + graph GQL + vector in one query. Best for globally consistent, multi-site deployments with regulatory traceability requirements.

CockroachDB
pgvector · C-SPANN

Distributed vector indexing via C-SPANN (v25.2). REGIONAL BY ROW keeps embeddings close to where they were generated. pgvector-compatible SQL. Multi-region data residency aware.

SingleStore
HNSW · IVF · HTAP

HNSW and IVF via Faiss, in-memory for sub-millisecond ANN search. HTAP handles real-time detection writes and historical trend analytics in one engine — no ETL required.

YugabyteDB
pgvector · USearch HNSW

USearch HNSW + Vector LSM storage. pgvector-compatible. Geo-partitioned tablespaces keep per-site embeddings local while a global aggregate view remains queryable centrally.

TiDB
HNSW · HTAP · GraphRAG

Native VECTOR type + HNSW index + TiFlash HTAP. GraphRAG support — knowledge graph traversal (defect → batch → supplier) combined with vector similarity for root cause retrieval.

Sightlinq detects. SchemaShifts governs the database that takes it further.

Customers who want vector search, RAG, or MCP on top of their Sightlinq detection data can adopt any of the six SchemaShifts-governed databases that support it. Fluxor can help you choose the right database for your deployment — air-gapped, multi-site, or cloud — and get the schema governance in place.

See the Full Architecture →

SchemaShifts

Schema governance for
distributed databases.

Versioned migrations, immutable audit logs, and distributed locking across Cassandra, Spanner, DynamoDB, CockroachDB, YugabyteDB, and more. SchemaShifts has its own home.

Apache Cassandra Google Spanner DynamoDB CockroachDB YugabyteDB Vitess TiDB Google Bigtable SingleStore
Visit SchemaShifts.com

Sightlinq · Visual AI Platform

From Raw Image
to Production Model.

Annotation, training, and deployment — unified in one interface that runs on your network, on your hardware, with your data.

01
Capture
Edge devices upload images automatically. Content-hash deduplication — no file is ever synced twice.
02
Annotate
Round 1: manual. Round 2+: the trained model pre-draws boxes. Annotators correct only mistakes.
03
Train
One click. Runs on your own hardware — GPU or CPU. Live status in the browser. Notifications on completion.
04
Deploy & Loop
Model deployed as live inference. Becomes the auto-annotator for the next batch. Faster every round.

The loop gets faster every round.

A 500-image batch that takes 8–10 hours to annotate manually takes 30 minutes by Round 4. By Round 5, it's a spot-check.

0.894
mAP50 best class
83 min
CPU-only training
27
Auto-detections
Full Sightlinq Overview