Your Infrastructure. Your Rules.
Zzeti Zeka is an LLM-agnostic enterprise AI platform that lets organizations run local LLMs, AI agents and RAG applications on-premise or in an air-gapped network — without sending sensitive data outside their own infrastructure. Private cloud, public cloud, Apple Silicon edge or commodity NVIDIA GPU: AI Gateway, autonomous agents, observability and compliance, closing the loop from detection to impact.

Autonomous agents that reason, plan, and act. MCP-powered tool access with built-in guardrails. Detect anomalies, diagnose causes, assign actions, measure impact — closed loop.
Unified API across 30+ LLM providers. Semantic caching, semantic routing, and token-budget management. Use the right model for the right workload.
Hierarchical permission model: Store → Region → Headquarters. Every query, every action, every output — governed by role.
Model Context Protocol connectors for the systems you already run: Nebim V3, Google Workspace, Logo, SAP, and more.
Enterprise-grade controls: PII masking, WAF, IP firewall, geo-blocking, secret detection. KVKK, GDPR, ISO 27001, SOC 2, HIPAA, PCI DSS aligned.
Visual workflow builder. Conditional logic, parallel execution, human-in-the-loop approval. Drag, drop, ship.
Run open-weight models on your hardware. Ollama, vLLM, Llama.cpp, LoRA fine-tuning. No token costs for high-volume predictable workloads.
Run on private cloud, public cloud (AWS, Azure, Huawei), Apple Silicon edge, or commodity NVIDIA GPU hardware. Pick the deployment that matches your sovereignty rules and workload shape.
Desktop-class AI inference on NVIDIA's Grace Blackwell GB10 — 1 PFLOP FP4, 128 GB unified memory. Run Zzeti with 70B-parameter open-weight models locally, no cloud token costs, no data leaving your office. Pair two DGX Sparks for 405B-class workloads. Perfect for retail HQs, factories, hospitals, and government — anywhere data sovereignty matters and a rack is overkill.
A governed data lake for agents — sources, catalog, certified and trusted zones — plus document collections and knowledge bases with routing triggers. Query Bench runs SQL & MDX through MCPs, never a direct database connection.
Actions Inbox routes approvals, inputs, reviews, escalations and anomalies to the right person. Agents message people proactively; people approve, correct or stop them — every decision is logged.
Evaluate agents with an LLM judge against test cases and pass thresholds before they go live. Compare the same agent across different LLMs side by side — streaming, tool calls and cost.
In retail, wholesale and manufacturing, money rarely leaks through one big hole. It seeps out through a few lines of the P&L: the product that isn't on the shelf, the cost increase priced in too late, the markdown made at the wrong moment, the cash sitting in the warehouse. Specialist software usually tackles one of these at a time — one tool for pricing, another for replenishment, a third for campaigns. Zzeti runs them as agents on a single platform, on your own data and your own infrastructure: it detects the deviation, explains the cause, assigns the action and measures what it earned.
Customers don't buy what isn't on the shelf — and the item that sold out in one store is often sitting in another store or in the warehouse.
Zzeti spots stock-outs days ahead at store × product level and drops a replenishment or transfer proposal into the right person's Actions Inbox for approval.
Stock that exists on paper but not physically blocks automatic reordering — the item quietly drops out of sales and nobody notices.
Zzeti flags products whose sales flat-line while stock is still on record, assigns a count task to the store and gets the item back on sale once the record is corrected.
Reflecting currency and cost increases in prices too late silently erodes margin; raising prices where customers are price-sensitive loses the sale.
Zzeti tracks cost, demand and price together, lists the products whose margin is eroding and those with room to price, and proposes prices together with the reasoning and the query behind them.
Discount too early and you burn margin; too late and you are left with dead stock at season end. Campaigns nobody measured get repeated.
Zzeti proposes markdown timing and depth from in-season sell-through, measures what past campaigns really returned and flags loss-making ones before they are repeated.
Slow, low-contribution products occupy shelf and warehouse space — space and budget that could go to the products that actually pay.
Zzeti calculates contribution margin and turnover per product and location, and recommends reorder, markdown or delist for each item.
Over-buying ties cash up in the warehouse, under-buying loses sales — and buy decisions often rest on last year's numbers and gut feel.
Zzeti combines the demand forecast with payment terms, currency and supplier lead times, and recommends when and how much to buy together with the cash impact.
Sending everyone the same offer burns the campaign budget, and a loyal customer who is drifting away is noticed only after they have gone.
Zzeti predicts who is likely to buy what, and when, from loyalty and CRM data, flags customers who are drifting away and delivers a personal offer over WhatsApp or e-mail.
Where prices move every day — used vehicles, equipment, commodities — a wrong purchase price kills the profit before the deal starts, and every extra day in stock costs value.
Zzeti reads market and competitor prices alongside your own past deals, proposes a profitable price range for buying and selling, and warns early about stock that is losing value.
The numbers are in the report, but answering “why did sales drop?” takes days — and by the time a decision is made, the opportunity is gone.
Every morning Zzeti finds the deviations in sales, margin and stock, explains the cause and assigns the action to the right person; management can ask follow-up questions in plain language and see the query behind every answer.
Scenarios are illustrative; results depend on data quality and on the scope of connectors and integrations in each deployment.
Zzeti Zeka is not a chat window wrapped around a model. Five product areas cover the whole lifecycle: building agents, feeding them governed data, running any model, automating the work, and keeping people and policies in control.
Feature map mirrors the live Zzeti Zeka console. The scope of individual connectors and integrations depends on the deployment.
Six AI use cases purpose-built for retail operations. Native Nebim V3 integration via MCP — flagship deployments at leading Turkish retail brands. Compatible with other retail ERPs through additional MCP connectors.
AI fed by Nebim V3 sales and stock data routes the right product to the right store at the right time. Reduces overstock and stockouts.
Sales forecasts by season, region, and channel. Historical sales data trained into predictive models that lower forecast error.
Automated price and discount optimization based on stock depth, competitor data, and customer behavior. Margin and sales lift together.
Income/expense analysis detects cash flow deviations before they happen. Proactive alerts shorten the cash cycle and reduce logistics costs.
AI fed by Nebim CRM and loyalty data generates customer-specific recommendations and campaigns. Customer lifetime value increases.
Store performance analysis, employee productivity tracking, return/loss analysis, automated reporting. Total operational costs go down.
Source benchmarks: McKinsey, Nationwide Group, IHL Group
In Türkiye's mould, die, press, casting, machining and plastics SMEs the picture is mostly the same: strong production know-how, thin digital foundations. Production is tracked in spreadsheets, orders travel over messaging apps, the ERP is missing or partially used, maintenance is reactive and quotations depend on a few experienced people. These are not AI problems yet — but they are exactly where an agent platform pays off first, because it can read what already exists and put structure around it.
Quotation depends on a few experienced people: reading the drawing and estimating material, machining time and tooling takes days, and slow answers cost orders.
Worker agent · RAG · Actions InboxShift output, scrap and downtime are collected by hand — in spreadsheets or messaging apps — so the numbers arrive late and are hard to trust.
WhatsApp agent · Context Lake · BoardsPress strokes, furnace hours and mould shot counts are rarely tracked systematically; maintenance is reactive and unplanned downtime arrives at the worst moment.
Scheduled runs · Messages · Anomaly detectionFinal inspection is manual and visual; defects escape to the customer and come back as PPM figures, claims and rework.
Local models · Edge GPU · WorkflowsDemand planning relies on experience and informal customer signals; raw material is bought late or at the wrong price and capacity swings between idle and overloaded.
Forecasting · Query Bench · BoardsSet-up parameters, customer specifications, quality procedures and the fixes for recurring problems live with a few experienced people and in documents nobody opens.
RAG · Collections · Role-based accessManagement wants plant KPIs at a glance without exposing financial figures to everyone — so dashboards either show too little or never get built.
Boards · Role-based access · Query BenchCustomer drawings, recipes and prices are confidential — often under NDA — which rules out sending them to public cloud AI services.
On-prem · Air-gap · DGX SparkScenarios are illustrative; the scope of connectors and integrations depends on the deployment.
Every component runs inside the perimeter you choose. No telemetry, no phone-home, no external API calls unless you explicitly configure them. Your models, your data, your rules.
Open-weight models such as Qwen, Llama and Mistral run on your GPU with vLLM or Ollama; Zzeti adds what a company needs around them — role-based access, RAG over your documents, MCP connectors to your ERP, agents, guardrails and an audit trail — with zero external calls if you choose an air-gapped installation. It is the platform for teams in Türkiye that want to work with a local LLM without their data leaving the company.
On-premise local LLM platform in Türkiye: the full guide →Zzeti Zeka is an LLM-agnostic enterprise AI platform. It runs autonomous agents, an AI Gateway across 30+ LLM providers, role-based access, and MCP integrations for systems like Nebim V3, Logo, SAP, and Google Workspace — on infrastructure you control (private cloud, public cloud, Apple Silicon edge, or NVIDIA GPU). Skyloop Cloud is the authorized reseller and deployment partner.
Zzeti works on the P&L lines where money quietly leaks: products missing from the shelf (lost sales), cost increases priced in too late (margin), markdowns made at the wrong time, slow products and cash tied up in stock, and customers drifting away. Agents run on your own sales, stock, cost and customer data: they detect the deviation, explain the cause, assign the action to the right person for approval and measure the result. Instead of buying separate tools for pricing, replenishment and campaigns, all of it runs on one platform on your own infrastructure.
Zzeti runs entirely inside a network perimeter you define — with zero external API calls, no telemetry, no phone-home. All model inference, orchestration, and data processing happen on hardware you own. Kubernetes-native with Terraform IaC, deployable on bare metal, private cloud, or hardware like NVIDIA DGX Spark. Suitable for regulated industries, government, and any environment where data cannot leave the perimeter.
Zzeti includes enterprise-grade controls purpose-built for KVKK requirements: PII masking (automatic detection and redaction of personal data before it reaches any model), role-based access control with Store → Region → HQ hierarchy, IP firewall, geo-blocking, secret detection, and full audit logging of every query and action. Aligned with KVKK, GDPR, ISO 27001, SOC 2, HIPAA, and PCI DSS. Combined with air-gapped deployment, no personal data ever leaves your infrastructure.
Zzeti's AI Gateway provides a unified API across 30+ LLM providers — including OpenAI, Anthropic, Google, AWS Bedrock, Azure OpenAI, and Turkish sovereign models. It also runs local open-weight models via Ollama, vLLM, and Llama.cpp with LoRA fine-tuning support. Semantic routing sends each request to the smallest capable model, semantic caching reuses responses for similar queries, and per-team token budgets keep spend predictable.
Zzeti's native Nebim V3 MCP connector exposes sales, stock, CRM, and loyalty data to AI agents in real time. Live deployments at leading Turkish retail brands power six use cases out of the box: smart product allocation, demand forecasting, dynamic pricing & campaigns, cash flow optimization, personalized sales, and operational efficiency. Compatible with other retail ERPs through additional MCP connectors.
Through MCP connectors — never a direct database connection. Agents and Query Bench run SQL/MDX through the MCP, the Context Lake holds governed copies in certified and trusted zones, and document collections feed RAG. Every query is logged together with its trace.
Yes. Model Hub pulls open-weight models from Hugging Face; GPU Servers deploys them with vLLM or Ollama on local, remote or Kubernetes GPUs, including NVIDIA DGX Spark edge nodes; Fine-tune Studio adapts a deployed model to your data and lets you test it before promoting. Cloud LLMs and local models sit behind the same gateway with load balancing and failover.
Worker agents run against explicit goals with supervisor and critique agents. Anything that needs a human — approvals, inputs, reviews, escalations, anomalies — lands in the Actions Inbox and the Workflow Dashboard's human queue. Guardrails filter inputs and outputs, AI Judge evaluates agents against test cases before release, and Monitor keeps every session, trace and cost visible.
Yes — that is the most common starting point in manufacturing SMEs. Agents read spreadsheets, e-mails, PDFs and WhatsApp messages as they are, extract structured data into the Context Lake and validate it. When an ERP exists (Logo, SAP, Nebim or custom), MCP connectors read and write it with approvals; when it does not, the Context Lake becomes the first single source of truth. You do not have to finish an ERP project before starting with AI.
In our experience the fastest returns come from four places: AI-assisted quotation (hours instead of days, less dependence on a few experts), maintenance reminders for presses, furnaces and moulds (fewer unplanned stops), structured shift and scrap data captured from messaging apps and spreadsheets (decisions on numbers people trust) and vision-based quality control at the line (defects caught before the customer). Demand forecasting and a management cockpit follow once the data is flowing.
Yes. Zzeti runs on your own server, on an NVIDIA DGX Spark or in a private cloud, fully air-gapped if required — open-weight models, zero external calls, no telemetry. Customer drawings, recipes and prices never leave the plant network. If you later want cloud LLMs for non-sensitive tasks, the AI Gateway routes only what you allow, with PII masking in front of every model.
Yes — that is the core use case. Zzeti runs local open-weight models, agents and RAG on your own servers, in a private cloud in Türkiye or in an air-gapped network; data, logs and documents stay inside. Skyloop installs and operates it. See the on-premise local LLM guide for the data flow, hardware options and a comparison of deployment models.
No. There is no telemetry, no phone-home and no external API call unless you configure one; an air-gapped installation keeps working with the internet unplugged. Updates and new model files are brought in through the maintenance process you approve.
Deploy in minutes. Scale without limits. Keep every byte on your hardware.