AIFab · LLM workspace

Every model, assistant and tool in one workspace.

AIFab puts one gateway in front of every language model, and builds assistants, knowledge bases and workflows on top of it, with MCP tools wired in. It installs inside your network.

Crudfab / Products / AIFab

A gateway, an application builder and a tool hub. In one product, sharing the same keys, limits and audit trail.

Three layers, one platform.

Teams reach every model through the gateway, build on it in the workspace and connect their own systems as tools.

Gateway

One endpoint for every model

OpenAI, Anthropic, Gemini, Bedrock, Mistral and your own GPU servers behind one address, with keys, quotas, masking, routing and metering.

Workspace

Assistants, knowledge and flows

Upload documents into knowledge bases, combine them with a model and tools into an assistant, and chain steps into workflows with human approval.

Tools

MCP built in

Register MCP servers once and let assistants use your databases, ticket systems and internal services, with every argument scanned and every credential sealed.

What happens to a request on its way to the model.

Applications keep their OpenAI or Anthropic SDK and change only the address and the key. The rest happens in the gateway, in this order.

01

Key check

Keys are matched as keyed HMAC-SHA256 digests. The plain key is never stored.

02

Masking

National IDs, tax numbers, IBANs and 16 other identifier kinds are masked before the call leaves.

03

Quota and fair share

Requests, tokens, concurrency and budget are checked together, in one atomic step.

04

Routing

To an outside provider or to the least-loaded of your own replicas, only among models the key is granted.

05

Record

A usage event and a double-entry ledger posting, written to disk before the model is even called.

Workspace

Build assistants on the same gateway your applications use.

Every assistant call goes through the same keys, limits, masking and audit as any other request.

  • Knowledge bases from PDF, Word, Markdown and text files: chunked, embedded through the gateway and stored in Qdrant or pgvector.
  • Search stays inside the tenant, and a deleted document disappears from the results with all its chunks.
  • An assistant combines a model, a knowledge collection and MCP tools, and drops into any web page as one embeddable component.
  • Workflows chain model calls, HTTP tools, conditions, loops, timers and human approval steps, and survive restarts.
  • The console has more than sixty screens for building, running, watching and governing, in Turkish, English and Arabic.
Tools

Your systems become tools the assistants can use.

MCP servers are registered in the platform, not in each application.

  • Assistants call registered MCP tools; tool arguments and results pass through the same personal-data guard as prompts.
  • Provider and tool credentials are sealed with AES-256-GCM under a separate key for each secret, bound to tenant and purpose, and never reach the caller.
  • Coding agents such as Claude Code, Codex CLI and Cline work through the gateway against your in-house models.
  • Outbound calls resolve DNS once and refuse link-local, metadata and multicast addresses.
Personal data

TCKN and IBAN are masked before the model sees them.

Built for Turkish and Gulf data, and applied while the answer streams back, not after.

  • Checksum validation for TCKN, YKN, VKN, the public tender number (İKN), and national IDs of Saudi Arabia, the UAE, Kuwait, Qatar, Bahrain and Egypt.
  • Text is normalised first, so Arabic-Indic digits, invisible characters and look-alike letters cannot slip a number past the scanner.
  • A value can be removed, replaced with a typed label, or held in a vault and put back into the answer for the user.
  • No byte reaches the user before every finding is settled, and if the scanner cannot answer, the request is refused.
Shared GPUs

Fair share that more keys cannot game.

When capacity is short, quotas and weighted classes decide who waits, and batch jobs cannot starve interactive users.

  • Fairness is applied to the person before the key.
  • Replicas are chosen by live load: work in flight, engine queue, KV-cache use and recent time to first token.
  • A failing replica is ejected automatically, and retries happen only before the first token.
  • Automatic routing can narrow the models a key may use but never widen them, and each decision is recorded with its reasons.
Installation

Installs without internet, and checks its own package first.

The offline package carries its images, a software bill of materials for each one and a signed manifest.

  • Before anything loads, the manifest signature is checked against a fingerprint delivered through a separate channel, then every file checksum.
  • Single server with a first-run wizard, a high-availability layout with a failover front door, or a Helm chart on your own Kubernetes and registry.
  • The licence is an offline signed file. A licence problem only pauses new requests; security, audit and data access never depend on it.

Built for the security team that has to sign off.

01

One endpoint, many protocols

Chat Completions, Responses, Messages, embeddings, rerank and OCR, translated to whatever the upstream model speaks.

02

Corporate identity

OIDC, SAML 2.0, LDAP and SCIM 2.0 provisioning, with TOTP, passkeys and recovery codes as second factors.

03

Tamper-evident audit

Each audit record carries the SHA-256 of the one before it, so an exported chain can be checked on its own.

04

Billing that survives a crash

Usage is on disk before the model call, and the ledger only accepts new entries.

05

Tenant isolation

Every query names its tenant, row-level security backs it up, and caches are partitioned per user.

06

Maker-checker changes

Sensitive configuration changes wait for a second person's approval.

07

Fails closed

If its configuration goes stale, its quota store goes away or its scanner stops answering, the gateway refuses new work.

08

Telemetry without content

Traces and logs carry ids, codes and timings, never prompt text, keys or client addresses.

See AIFab on your own network.

Request a briefing
Mobile and WhatsApp
+90 540 278 33 22
Email
hello@crudfab.com