Proxed AI

Key features

• Apple DeviceCheck attestation on every request The documented iOS flow fetches a device token and sends it in an x-device-token header, so hardware-level verification blocks emulators, scripts, and jailbroken devices before they reach quota.[1][2]

• Split-key protection for provider credentials Only a harmless key fragment ships inside the app while the sensitive half stays on the proxy server, directly answering the hard-coded-key extraction problem.[1]

• One-line endpoint swap with no SDK Integration means changing the API URL and headers, with Swift sample code for vision analysis, so adoption rarely means rewriting application code or adding dependencies.[1]

• Three provider proxies plus structured endpoints Documented proxies cover OpenAI, Anthropic, and Google AI model families, alongside vision, text, PDF, and image-generation analysis APIs.[1][2]

• Visual schema builder for structured outputs Teams define JSON response schemas visually and the proxy enforces consistent, type-safe model output for downstream parsing.[1][2]

• Per-project rate limits and spending ceilings Granular guardrails cap usage per project with alerts before budgets blow, addressing the runaway-bill failure mode of a leaked key.[1][2]

• Built-in observability and audit trails Usage monitoring, lightweight metrics and health endpoints, and compliance-oriented audit trails expose what each project spends and calls.[1]

• Free self-hosting on standard services The open-source codebase self-hosts with Supabase, Vercel, and GitHub accounts and no usage limits, which suits privacy-focused teams and regulated deployments.[1][2]

Who will love it

• iOS teams shipping AI features without a backend The endpoint swap plus DeviceCheck gives hardware-backed key protection quickly, with no server code to write or operate.[1][2]

• Indie developers worried about key theft and bills Split keys plus per-project ceilings convert an existential leaked-key incident into a capped, alerted event.[1]

• Privacy-focused teams that self-host everything The open codebase on your own Supabase and Vercel accounts keeps prompts, keys, and logs inside infrastructure you control.[1][2]

Who should avoid it

• Teams shipping beyond Apple platforms DeviceCheck attestation is iOS-specific, so Android, web, or desktop clients sit outside the core protection story.[1][2]

• Buyers needing open self-serve cloud onboarding New cloud registrations are paused during the vendor's direction change, so only existing accounts and self-hosting are live paths today.[1]

• Enterprises needing broad coverage and attestations Three provider families, email-led support outside the Enterprise tier, and unstated data regions fit small teams better than compliance-heavy procurement.[1][2]

Alternatives and compatibility