grafty

For IT & security

Your teams want AI app builders. Give them one you can approve.

Employees are already trying cloud AI app builders with company data. Grafty gives them the same experience inside your rules: it runs on your infrastructure, calls your models with your keys, and lets you decide which models, budgets and people are allowed.

Your keys, your data

You signed an enterprise AI agreement. Your app builder should use it.

On cloud AI builders, your prompts and code go through their servers under their model contract. Grafty runs inside your network and calls your models with your keys: your OpenAI or Anthropic enterprise agreement, your Azure or Bedrock endpoint, or a model running on your own hardware. We never see your data.

  • Your OpenAI and Anthropic enterprise agreements: the preferred setup
  • Azure and Bedrock-style enterprise endpoints, or fully local models
  • Air-gapped licence available: no outbound connection at all

Bring your own provider - or run fully local

  • OpenAI
  • Anthropic
  • Google Gemini
  • Mistral
  • DeepSeek
  • Moonshot Kimi
  • Meta Llama
  • xAI Grok
  • Cohere
  • Perplexity
  • Qwen
  • Hugging Face
  • Groq
  • Together AI

Cost control

Every app has a price tag. IT sets the limits.

Grafty shows what every app costs, across everyone who worked on it, down to input, output and cached tokens. IT decides which models are approved, which are manual only and which are blocked, and sets a maximum price Auto will never exceed. The biggest saving isn't a cheaper model. It's building once instead of four times.

  • Live spend per app, all contributors combined
  • Models: Approved, Manual only or Blocked
  • Auto limits: maximum input and output price per 1M tokens
  • Budgets per user, project and team, enforced before the call
  • 0% markup: you pay providers directly
0%

Markup on model usage

3

Budget scopes: user · project · team

100%

Limits enforced before the API call

Builder Chat header with spend, input, output and cached token breakdown for one app
Model approval settings with approved, manual-only and blocked models and Auto price limits

Example scenario.

Example scenario.

Example scenario

Estimate model spend on your own keys

Move the sliders to match your team. Your model provider bills you directly at its own prices, and Grafty adds no markup.

25
10
$0.40

Estimated model spend per month

$433

≈ $17.33 per person, paid to your provider. Set budgets per user, project and team.

Illustrative only. Real cost depends on your models, prompts and provider prices. A change can be a new app or an edit to one.

Security & trust

Built for the security review you're about to run.

Architecture overview, threat model, SBOM, and DPA available on request. Built to pass the security review, not work around it.

Single-tenant, customer-operated

Each customer runs their own Grafty instance on their Linux infrastructure. There is no shared SaaS plane.

Isolated runtime per app

Every generated app runs in its own isolated environment with resource quotas - isolation by default.

Encryption everywhere

All inter-service and ingress traffic over TLS. Provider keys and integration tokens encrypted on disk on the instance.

Immutable audit

Append-only audit events for privileged actions, scoped by role and exportable for SIEM ingestion.

SSO and RBAC

Single sign-on on the Enterprise tier, with instance admin, developer and viewer roles and per-app access controls.

Your licence, your choice

Two licence options: fully air-gapped, or a licence-status ping that never carries customer data.

Where data lives

Inside your network boundary:

  • Builder UI
  • Source code
  • Git history
  • Previews
  • App data
  • Audit logs
  • Integration credentials

We do not receive, store, or process your prompts, code, or runtime data.

Compared with cloud AI app builders

What changes when the builder runs inside your network.

Grafty compared with Lovable, Replit, Base44
FeatureGraftyLovableReplitBase44
Where the builder runsOn your own infrastructure, inside your networkLovable’s cloud. Deploying apps to your own AWS account is in private preview for EnterpriseReplit’s cloud. Enterprise lists single-tenant and private networking optionsBase44’s cloud
How AI usage is paidYour model provider bills you directly. Grafty adds no markupCredits included in each planCredits, or your own provider key billed by the providerMessage and integration credits
Use your own model keysYes: OpenAI, Anthropic, Google Gemini, OpenRouter or a self-hosted modelNot listed publiclyYes, documented for OpenAI, Anthropic, Google and othersNot listed publicly. Paid plans choose from models Base44 provides
Building togetherOne shared Builder Chat, plus comments pinned on the live previewShared workspaces with unlimited membersUp to 15 collaborators on ProMulti-user editing on every plan
IT controls over models and spendApproved, manual-only and blocked models; budgets per user, project and teamPer-member monthly credit limitsAdmins control AI Integrations; Enterprise limits models to zero-data-retention endpointsNot listed publicly
Single sign-onEnterprise tierEnterpriseEnterpriseEnterprise

Compared on November 2, 2026 using each company's public website. Lovable, Replit and Base44 are trademarks of their respective owners. Grafty is not affiliated with, endorsed by or sponsored by them.

Sources: Lovable pricing · Lovable for enterprise · Deploy on AWS announcement · Replit pricing · Replit AI Integrations docs · Base44 pricing · Base44 for enterprises

Start small

Start with one team.

You don't need a company-wide rollout to find out whether Grafty works for you. Prove it with one team, alongside your security review.

  • 1 instance
  • Up to 5 users
  • Per-user token budgets
  • Standard legal docs
Start a pilot
  1. 01

    Pick one team and one workflow.

    Start with the report, tracker or process that people rebuild by hand every week.

  2. 02

    Run Grafty in your environment.

    A pilot runs as one instance on a single server, connected to your own model keys.

  3. 03

    Build together, review together.

    The team builds real apps while your security team reviews models, budgets, access and the audit trail.