Sell private AI access with a brand customers can trust.

blueberry Ai turns model access into a clear subscription product: customers choose a monthly plan, receive protected gateway access, and use supported AI routes through your branded endpoint while provider credentials stay private on the server.

View live-style example View subscription plans

Illustrative monthly volume€100,000

Illustrative accounts1,240

Provider keys exposed0

Checking gateway Provider keys never shown to customers Private customer access

customer blueberrry.net blueberry-reasoning

Explain private AI routing in one paragraph.

blueberry keeps provider credentials server-side, meters usage, and returns a clean response through the customer's own access key.

Plan Plus monthly

Example flow Private gateway, monthly plan, protected routing.

Customers see one clean access layer. Provider keys stay hidden, subscription status stays visible, and requests move through your branded API. All financial figures shown here are illustrative.

Example

A customer chats through your private gateway.

This is the kind of product moment customers should understand immediately: they choose a monthly plan, use a blueberry access key, and never receive your upstream provider key.

RouteReasoning model via blueberry

SubscriptionPlus monthly

PrivacyProvider key hidden

blueberry Ai chat private route

Customer endpoint blueberrry.net/v1/chat/completions

Model route blueberry-reasoning

Plan status Active

Customer

Explain mixture-of-experts models in a short onboarding note.

Reasoning route

Mixture-of-experts models activate only the specialist parts needed for each request, so responses can stay strong while compute stays efficient.

PlanPlus

Usage cycleMonthly

AccessActive

What blueberry Ai is

A commercial wrapper around AI models, built for selling access clearly.

Most AI products start as a direct provider integration. That is fine for a prototype, but it becomes awkward when real customers need invoices, limits, support, and a safe way to use your service. blueberry Ai gives the business a front door and keeps the sensitive machinery behind it.

The goal is not to look like a complicated admin system. The goal is to make the offer understandable: choose a plan, get access, use the API, and let the gateway measure what happened.

Customer sees

A clear monthly subscription

Plan pricing, included access, cancellation controls, and a clean support path.

Your server owns

Provider keys and routing

The upstream API key stays out of the browser and away from customers.

You monitor

Usage, subscriptions, and revenue

Requests and subscription events are recorded so the business can be managed.

Platform

Designed for teams that need AI revenue to look like a business, not a pile of keys.

A normal AI integration gets messy fast: provider accounts, customer access, payment status, token usage, and support questions all live in different places. blueberry Ai turns that into one operating layer with a simple public API and a private server-side control plane.

ProviderRoutes live server-side

AccessCustomer keys, not provider keys

MoneySubscriptions, invoices, usage limits

VisibilityUsage, requests, margin signals

What It Controls

The practical pieces behind a subscription AI service.

Provider abstraction

Customers call blueberry first. The server forwards to the configured model provider, so upstream credentials never appear in website JavaScript or customer apps.

Subscription access

A customer chooses a monthly plan, receives a private access key, and uses protected API routes within that plan.

Usage records

Requests, token estimates, pricing rules, and account activity are recorded server-side for operations and customer support.

Margin awareness

Public prices can sit above provider cost. That gives you a clearer view of revenue, spend, and when pricing needs to change.

Workflow

From payment to model response, every step has an owner.

Customer chooses a plan

Checkout happens on Paddle's hosted payment surface while blueberry waits for a signed subscription event.

blueberry issues access

The customer receives a private `bb_...` key. The server stores a protected record and keeps the provider key hidden.

Apps call the gateway

Requests use familiar `/v1/chat/completions` style routes, then blueberry forwards to the configured model.

Usage becomes visible

Operations can review request volume, subscription events, account status, and pricing assumptions in one place.

Operations

A calmer euro view of revenue, usage, and customer access.

The operational layer is intentionally quieter than a full analytics suite. It focuses on the numbers a small team needs to run the gateway with confidence.

blueberry operations illustrative dashboard, not live sales

Illustrative subscription revenue €100,000 interface example only

Requests 4.80M last 7 days

Active keys 1,240 customer access

Policy pass rate 98.6% gateway checks

Traffic

Request activity

protected

Models

Routing table

Defaultblueberry-standard

Premiumblueberry-reasoning

Browser exposureblocked

Provider keyserver only

Ledger

Example subscription activity

sample view

Harbor Studio€30/moPro active

Northline Apps€20/moPlus active

Founders Lab€30/morenewed

SearchPilot Tools€10/moBasic active

API

Use familiar routes while keeping credentials private.

The public contract can stay simple for customers. Your internal provider choice, pricing, and access policy remain on the server.

curl https://blueberrry.net/v1/chat/completions \
  -H "Authorization: Bearer YOUR_BLUEBERRY_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "blueberry-reasoning",
    "messages": [
      { "role": "user", "content": "Write a short welcome message." }
    ]
  }'

Gateway routes

/health public service status
/billing/config billing readiness
/v1/models protected model list
/v1/chat/completions protected chat route
/v1/usage protected usage summary

Billing

Simple monthly plans with secure Paddle checkout.

Choose a plan here, then enter card details only inside Paddle's hosted checkout. Each plan renews monthly and its usage allowance resets with the billing cycle.

Monthly access

Choose your blueberry plan

Plan Basic €10/month 1M combined tokens per billing cycle Private gateway access Usage summary Recommended Plus €20/month 3M combined tokens per billing cycle Multiple model routes Email support Pro €30/month 7M combined tokens per billing cycle Highest monthly allowance Priority support

Loading Paddle checkout configuration.

Monthly renewal. Cancel before the next billing date to avoid a new charge. By continuing, you agree to the Terms, Privacy Policy, and Refund Policy.

Secure checkout

Payment details stay with Paddle

blueberry receives the verified subscription result, plan, and customer reference. Raw card numbers never reach this server.

ProviderPaddle

VerificationSigned webhook

Card storageNot on blueberry

Selected plan

Basic

Allowance1M tokens

RenewalMonthly

Usage resetEach billing cycle

Checkout state

ModeSandbox

Payment statusloading

Access provisioningafter verified webhook

Security

Private access, clear boundaries, easier trust.

Provider keys stay server-side.

Third-party model credentials are read by the gateway service, not exposed to customer browsers.

HTTPS protects public traffic.

The public site and API routes are served through HTTPS on `blueberrry.net` and `www`.

Card data stays with Paddle.

blueberry stores verified subscription state and usage records, not raw card numbers.

Customer keys can rotate.

Access can be changed without replacing the upstream provider key or editing customer code.

About blueberry Ai

We are a product team focused on making AI access sellable.

blueberry Ai exists for founders, studios, and small teams that want to offer AI access under their own brand without exposing provider accounts or stitching together payments by hand.

We care about calm, explainable software. A customer should understand what they are buying. An operator should understand what was paid, what was used, and what needs attention. That is the difference between a pretty demo and a product people can actually use.

01Make the offer simple before adding more models.

02Keep secrets private even when the product is public.

03Show enough usage detail to support customers quickly.

Contact

Start the conversation without publishing private details.

Use brand contact channels for sales, support, and security messages. Personal addresses, home details, provider keys, and payment secrets should never be sent through the public website.

General hello@blueberrry.net Access requests, onboarding, and partnerships Support support@blueberrry.net Account, usage, billing, and gateway questions Security security@blueberrry.net Responsible disclosure and access concerns

Privacy-first launch

Private-first means the public site only shows brand channels: company mailboxes for conversations, a registered office or virtual business address for legal notices, and no provider keys, card details, or private credentials in public forms.