Reserve budget before the call
Conservative reservations check available budget before provider dispatch. Customer, project and scoped-key limits keep concurrent work within configured spending rules.
Oryndra · Pre-launch
Open for buyer evaluation · Pilot planned
Oryndra
LLM Spend Controller
Customer-hosted AI access with spending rules
Put spending rules in front of AI requests.
Control AI spending, onboard your team, trace usage to individual requests, and recover accounts with safeguards for saved conversations—all in one customer-hosted gateway and chat workspace.
Before a request reaches a model
A clear path from request to record
- 01
Team or app
A team member or connected app makes a request.
- 02
Policy check
Access, budget, and approval rules are checked first.
- 03
Allowed model call
An eligible request is sent through the customer-hosted gateway.
- 04
Usage record
The response and configured usage record are saved.
One connected operating flow
Spending rules. Team access. Saved work.
Bring the gateway, employee workspace and administrative controls together—from the first invitation to the audit record behind a request.
Control spending
Reserve budget before dispatch and trace costs from each person to each request.
Manage team access
Onboard with shared presets and recover accounts with safeguards for earlier chats.
Keep work moving
Reopen saved conversations, export supported media and use checkpointed workflows.
01 / Spending & accountability
Know who spent what. Control what happens next.
Set the rules before dispatch, then follow usage from the employee or application down to the individual request.
Approvals that respect budgets
Require human approval above a per-request threshold. Approval authorizes the request while customer, project and key budgets still apply.
Scoped keys, reusable defaults
Control allowed models, expiry, request rate and concurrency. Separate Users and Client keys pages offer searchable directories, key details, revocation and reusable key presets.
Employee-to-request spending
Filter by employee, API user, customer, project, provider, model, status or date. Open a provider card, drill into a request and export the matching usage as CSV.
Prices preserved with each request
Inspect the saved rate snapshot, input/output tokens and reported cache or reasoning subsets. Accounted costs and unresolved budget holds stay separate; later pricing edits do not rewrite earlier request rates.
Readable audits, clear reporting time
Search audit history by person, event and date. A server-synchronized UTC clock sits beside reporting; daily exports use UTC dates and search filters label their browser-time offset.
02 / Team access & recovery
Onboard a team. Keep recovery under control.
Give employees a consistent workspace policy, with individual sign-in, storage allowances and explicit recovery safeguards.
Presets and bulk invitations
Save shared model, budget and storage policies. Invite up to 50 employees per batch and download their unique private links as CSV. Readable assigned usernames are verified and read-only during setup.
Invites with a defined lifetime
Choose link validity from 60 minutes to 48 hours, also bounded by generation expiry. One-time token links verify the assigned account; enrollment returns to normal password and Authenticator sign-in.
Per-employee archive storage
Set a 16–1024 MiB allowance per employee, with 64 MiB as the default. Saved text and supported media share the quota, making storage policy an explicit onboarding choice.
Three deliberate recovery paths
Reset a password while retaining the existing Authenticator, replace an Authenticator while retaining the password, or recover both. Each recovery revokes existing sessions and retains the employee identity.
Earlier chats protected after full reset
Full recovery locks earlier chats until an authorized server operator unlocks them. Staff browser roles cannot read or unlock employee archives. Full recovery, operator unlocks and post-recovery access leave audit records.
Encrypted, write-only provider vault
Store provider keys with AES-256-GCM encryption and replace credentials without reading back existing secrets. Vault wrapping-key rotation is a separate operation. Authorized host operators remain trusted.
03 / Workspaces & integrations
Keep the conversation. Carry the work forward.
Saved conversations, portable exports and checkpointed workflows support work beyond a single browser tab.
Saved employee and admin chats
Encrypted conversation history persists across refresh and sign-in. Administrators have their own saved-chat list and reconnect a scoped key before continuing. Generation expiry preserves saved employee history.
Supported media, reviewed summaries
Use documented image and audio inputs with compatible routes. User-reviewed conversation summaries help manage longer conversations while keeping the user involved in what is carried forward.
Portable conversation exports
Export as TXT, JSON or self-contained HTML for offline reading. JSON and HTML can include supported media, keeping the conversation useful outside the workspace.
Workflows with saved checkpoints
Run ordered model steps with budgets and checkpoints. Opt-in recovery can resume eligible steps after confirmed provider quota rejection; uncertain or interrupted outcomes can require review.
Model routing and developer access
Configure routes and opt-in fallback paths, subject to provider support. Connect applications through the gateway API or cooperative Python SDK, with customer and project accounting boundaries.
Configured SSO and notifications
Google Workspace SSO supports explicitly authorized administrator identities. Configured Slack or Telegram endpoints can receive budget and security notices through the delivery worker, with retry handling.
Commercial acquisition & licensing
Exclusive acquisition & white-label enquiries are open.
Built as a head start for AI agencies, managed IT providers (MSPs), and B2B software teams looking to rebrand, integrate, and build on a working product foundation.
Option A · Full commercial control
Exclusive acquisition deal
privately
Acquire the Oryndra product foundation for buyer rebranding and commercialization, with final transfer terms documented in the signed agreement.
- Full rebranding and commercialization: Exclusive transaction, build and sell under the buyer’s own brand, subject to third-party component licences.
- Complete asset handover: product source, test suite, illustrated setup documentation, dependency notices, and support runbook.
- Support: 14 days handover support included.
Option B · Custom brand deployment
White-labeling offers
An alternative path for AI consultancies, managed service providers, and enterprise software teams interested in deploying Oryndra under their own brand. White-label scope and commercial terms are discussed separately.
- Your brand, controlled AI access: discuss logo, colour, and domain customisation for a client deployment.
- Multi-client governance: customer, project, and API-key budgets with usage reporting.
- Developer integration: discuss Gateway API and Python SDK integration with the buyer’s existing stack.
The acquisition and white-label paths are alternatives, not simultaneous rights grants. Third-party components remain subject to their own licences; definitive scope and transfer terms require a signed agreement.
Recorded pre-launch evidence
Evidence available for buyer diligence
The product walkthrough uses actual product UI captures with synthetic demo data. It is a narrated presentation, not a live interactive recording.
Owner-run token reconciliation
A recorded Groq request matched 80 input and 43 output tokens to the provider dashboard, with $0.295 settled at configured test prices. This was a free-tier call with simulated nonzero pricing.
Paid Gemini API counter matching
A recorded paid Gemini call preserved 31 input and 956 output tokens from the incoming API response, including reported thinking. The configured-rate calculation matched the settled $0.003609.
This verifies captured API counters and configured arithmetic. Provider dashboard/log differences are documented separately; provider invoice reconciliation is not established.
Restart and recovery checks
Owner-run restart checks preserved the recorded ledger. Employee tests covered password-only and MFA-only recovery with saved chats retained, plus full-reset archive locking, audited operator unlock and an unaffected second account.
Walkthrough and package review
A 13-part buyer walkthrough and a verified source package are available for evaluation, with updated setup guides, 23 documented screenshots and file-integrity records.
These are seller-prepared records, not an independent security certification or third-party audit.
Turnkey asset transfer
What the handover package includes
Materials are organised to help a buyer review, rebrand, and plan deployment with their product and engineering teams.
Product source
Gateway, employee chat portal, and cooperative Python SDK.
Tests and evidence
Test suite, recorded acceptance evidence, and walkthrough materials.
Illustrated setup guide
Step-by-step commands and 23 screenshots covering setup, onboarding, spending and recovery.
Runbook and notices
Command-based troubleshooting, third-party notices, CycloneDX/SPDX inventories and IP documentation.
Ready for review
Request the buyer pack
Ask questions, review the walkthrough, or discuss either commercial path.