Who operates Modelith
Modelith is operated by Mahdi (solo founder), a solo founder based in Algiers, Algeria. The product is one full-stack engineering effort (frontend, backend, infrastructure, billing, security, support), with a small set of named subprocessors for the parts that cannot be operated by one person — payments, email, hosting.
We are not a public company and we do not have outside investors at the time of writing. There is no parent company, no affiliated brand, and no white-label arrangement. The legal entity is Modelith.
Operating as a solo founder is a deliberate choice at this stage. Every byte of customer data flows through code that one engineer wrote, reviewed, and runs. The trade-off is capacity, not trust; we scale capacity through subprocessors and through automation, not by abstracting accountability.
Architecture and data flow
Modelith exposes an OpenAI-compatible HTTP API. Your client code sends a request to api.modelith.cloud using a mlth_ API key. From there the request flows through the governance plane, which decides which upstream model to use, what session budget remains, and whether the request should be served at all.
For BYOK, your provider key is decrypted in-process and the request bypasses OpenRouter; the request goes directly from the governance plane to the model provider you configured.
The governance plane is the layer that distinguishes Modelith from a plain router. It maintains a session state per request session, with a step counter, a budget, a tier, a fingerprint, and a halt history. On each request the governor checks the state and either allows, escalates, downgrades, or halts the request. The decision is logged and shown in the dashboard.
What we store, what we never store
Routing metadata we retain
- Request timestamp
- Model and provider selected
- Input and output token counts
- Estimated cost in USD
- Complexity score (1–10)
- Latency in milliseconds
- Session ID, when governor features are used
What we do not store by default
- Full prompt text
- Model completions
- Raw API keys (encrypted only, never logged)
- Decrypted BYOK provider keys
Optional product surfaces (dashboard chat, semantic cache, evaluation traces) may store prompt content; the relevant toggle is shown in dashboard settings and is off by default. See the Privacy Policy for the full retention and deletion story.
Uptime and status
Modelith targets 99.5% monthly availability for the routing API. This is a published goal, not a contractual SLA; we do not offer service credits at this stage. Live component probes (Redis, OpenRouter pool, database, billing webhooks) and incident history are available on the status page.
Subprocessors
The subprocessors that handle customer data on our behalf are listed in the table below. We notify active subscribers by email at least 30 days before adding a new subprocessor that handles personal data.
| Subprocessor | Role | Data handled | Region |
|---|---|---|---|
| Paddle | Merchant of Record | Billing, invoices, tax | United States |
| OpenRouter | Upstream aggregator | Prompts, completions (platform routing) | United States |
| Railway | Application & database hosting | Application data, primary DB | United States / Canada |
| Vercel | Frontend hosting | Static assets, edge traffic | Global edge |
| Resend | Transactional email | Recipient, email body | United States |
| Upstash Redis | Cache & rate limiting | Counters, session state (no prompts) | United States |
Customer support
We support customers by email. There is no live chat widget and no phone support. The targets below are the response time we aim to hit, not a contractual SLA:
- Security reports. Acknowledgement within 72 hours on business days, regardless of plan tier.
- Billing and refund questions. Acknowledgement within 1 business day.
- General product support. First response within 24 hours on business days (Monday–Friday, Africa/Algiers timezone).
- Paid plan customers. Priority routing; first response target 12 hours on business days.
Reach a human at founders@modelith.cloud. Security reports go to security@modelith.cloud. Billing and refund questions go to billing@modelith.cloud.
Linked policies
The full set of legal documents that govern the service is linked below. They are the authoritative source for any commitment made on this page; if a statement on this page ever conflicts with a policy, the policy controls.
- Privacy Policy — data we collect, how we use it, and your rights
- Terms of Service — the binding agreement for using the service
- Acceptable Use Policy — prohibited content and behaviors
- Refund Policy — 30-day money-back guarantee, wallet rules, and how to request
- Security — authentication, encryption, rate limits, and audit logs
- Cookie Policy — the single auth cookie and the localStorage we use