Familiar integration
Point your preferred HTTP client or SDK at one base URL. Chat, streaming, tools, vision and embeddings follow familiar request formats.
base_url="https://llm.grand-ice.com/v1"
A self-hosted AI platform for teams that are done watching usage meters drain their technology budget. Run capable open models behind one secure, provider-grade API.
Prototypes are cheap. Production is not. Once customers, agents and internal workflows start making millions of calls, every useful interaction becomes another line item.
Grandice changes the unit economics: invest in infrastructure once, then use it continuously without a vendor charging for every input and output token.
Move from hosted providers without rebuilding your application stack.
Point your preferred HTTP client or SDK at one base URL. Chat, streaming, tools, vision and embeddings follow familiar request formats.
base_url="https://llm.grand-ice.com/v1"
Prompts and model inference stay on infrastructure you operate—not in a third-party model provider’s cloud.
No per-token vendor invoice. Capacity is determined by your hardware, concurrency and operating policy.
Issue a unique key per team or application, restrict model access, set rate limits and review usage centrally.
Stable aliases decouple applications from model versions. Upgrade the model behind smart without touching client code.
Typed financial, legal, and market APIs separate deterministic analysis, caller-source metadata, privacy checks and professional-review requirements.
POST /v1/market/research/analyze
Read the financial agents white paper →
Read the legal contract intelligence white paper →
Read the market research intelligence white paper →
Grandice provides auditable, source-grounded domain workflows through developer-friendly APIs. Privacy Shield adds a local protection boundary for prompts, structured data and multimodal inputs before those workflows run.
Explore the privacy APIs →Python and TypeScript protection runs inside your application. Original values and reversible token maps stay in your process.
mode: "client"
Point an existing OpenAI-compatible application at a loopback proxy for policy enforcement, local media processing and safe rehydration.
localhost:8090/v1
Detect, mask or tokenize JSON with a single authenticated request. Original content reaches Grandice memory but is not written by the privacy layer.
POST /v1/privacy/redact
Zero-transfer applies only when protection runs in the client SDK or local sidecar. Hosted processing is zero-retention, not zero-transfer. Automated detection has limitations and high-risk outputs still require review.
Simple aliases make capability selection clear for developers and end users.
View model documentation →Client SDKs or the local sidecar can sanitize sensitive values before transmission. Cloudflare provides encrypted ingress, the authenticated gateway governs every request, and model weights remain isolated on the private host.
Separate credentials make access revocable and usage attributable.
Limit each key to the capabilities that application actually needs.
Protect finite local capacity from accidental loops and abusive traffic.
Ollama stays bound to localhost; only the authenticated gateway is published.
Versioned policies, residual checks and fail-closed processing prevent known sensitive data from silently bypassing protection.