Flexible model and deployment choices
Choose model, document processing and retrieval components that fit your data and deployment requirements. Organisation context travels with each request to keep access boundaries explicit.
Private AI workspace
Private AI workspace · Discuss your deployment
Give growing teams a ready path to private AI, grounded knowledge and governed assistants.
Is this the right product?
The current workspace supports a controlled local evaluation. Wider deployment requires production sign-in and verified access boundaries between users. Document search and model connections are agreed and tested for your setup.
Follow the work
In a controlled evaluation, a team selects an assistant, attaches authorised material and follows the result without exposing model credentials in the browser.
Controlled evaluation workflow
The gateway resolves the assistant configuration and available permissions. Select the tools allowed for the conversation; an empty selection disables tools.
A private AI workspace for small and mid-sized organisations. Bring assistants, document processing and internal knowledge together with on-premise deployment, access controls and an auditable activity history.
Run models, OCR and embeddings inside a controlled environment so organisational data stays within its intended boundary.
Keep tenants, principals, roles and capabilities isolated through an explicit context carried across every service boundary.
Give teams a focused chat surface for governed assistants, durable sessions and clear handoff to the work that follows.
Turn invoices, PDFs and visual documents into structured information with OCR, parsing and model-assisted extraction.
Connect embeddings, vector search, citations and document pipelines so assistants can answer from the organisation’s own knowledge.
Keep model, tool and side-effect history reviewable through API boundaries, idempotent actions and tenant-aware audit records.
Architecture & control
Essentials packages Pyrodit’s private AI building blocks into a focused workspace for organisations that need useful assistants and document intelligence inside their own boundary.
Choose model, document processing and retrieval components that fit your data and deployment requirements. Organisation context travels with each request to keep access boundaries explicit.
Document processing and retrieval components provide a foundation for connecting assistants to approved internal sources. OCR, search, source references and tool access must be validated together for the chosen assistant; file upload alone does not establish a working knowledge integration.
Admin, API, idempotency and audit surfaces provide a practical path from a private team workspace to governed Pyrodit services.
Use cases
Keep goods moving, production running and banking operations accountable. Explore workflows across business units, systems and approval boundaries.
Bring intercompany transactions, deliveries and accounting records across ERPs into one exception queue. Prioritise close blockers by exposure, materiality and accountable team.
Explore the workflow →Bring relationship managers, customer due diligence and operations into a shared case. Track legal entities, authorised representatives, missing evidence and review decisions together.
Explore the workflow →In practice
Explore the working steps, operational controls and evaluation boundaries behind the product.
A conversation starts with an explicit tool selection, bounded by the assistant, client and organisation permissions resolved by the gateway. An empty selection disables tools. Activity records distinguish completed, approval-pending, failed and cancelled work; approval previews expose a limited view of the proposed action instead of the full private conversation.
Files belong to a conversation and pass through gateway ownership, size and content checks. Uploads can be reconciled after an uncertain response without creating another file. Attachment storage does not itself grant a tool permission to read the file; deleting stored bytes also does not erase text already included in earlier messages.
The current chat workspace supports controlled local evaluation with gateway-managed history and model configuration kept on the server. After a connection failure, the interface checks the original request rather than automatically sending a new one. Production user sign-in and multi-user deployment acceptance remain prerequisites for a wider rollout; document and business integrations must be validated for the chosen assistant.
Works alongside
Combine the capabilities your process needs. Define how products share context, permissions and results across your workflow.
Move toward custom orchestration when the requirement goes beyond a focused assistant workspace into multi-step business processes.
Assess the chosen assistant, model and prompt configuration before broadening access or changing its permitted tools.
Build with Mindtro