Familiar integrations
Connect your applications through familiar chat and streaming requests.
Accentrust is planning unified model access and inference services for businesses in Canada and the United States. Connect Figena, Cilila AI, or your own applications to models that fit, with control over deployment, usage, and cost.

Figena connects business operations and finance. Cilila AI helps teams understand business context and move work forward. Accentrust’s infrastructure plans extend this foundation to unified model access and inference capacity for your own applications, as a service independent of the Figena business suite.
Tenant identity · scoped keys · TLS · request limits
Model, region and budget rules · no approved route → explicit error
Data requests use storage services; model requests use an approved inference route.
Owned or contracted capacity · agreed processing location
Only context selected under the application’s permissions reaches inference. Stored data is not automatically sent to models.
Segmented networks · power & cooling · physical access controls
Selected models · verified processing regions · disclosed data terms
Provider routes do not have direct access to the storage plane.
Responses return through the gateway. Saving results requires a separately authorized write to the data service.
Management and telemetry cover both deployment paths. They do not provide unrestricted access to customer content.
Model access, managed inference, and dedicated capacity, shaped around the needs of businesses in both markets.
We’re planning one model API for teams in Canada and the U.S., with more choice and clearer control. Public access is not yet open.
Connect your applications through familiar chat and streaming requests.
Compare capabilities, processing locations, and prices to find your fit.
Keep model selection and fallback within your approved regions and budget.
Manage access and usage by application, with clear permission boundaries.
See response times, errors, and usage together to spot what needs attention.
Understand usage rates and service fees before you commit.
We’re planning deployment options for teams in Canada and the U.S. Compare models, processing locations, and data terms around your workload.

Planned capacity in Vancouver, with processing and data terms tailored to your workload.
Explore authorized providers by model fit, processing region, and data requirements.
Deployment locations and data terms are confirmed before access.
Compare the complete data path alongside the model, including what is retained and who can access it.
Our intended policy excludes customer prompts and outputs from model training. Any external provider’s processing and training terms would be disclosed for the selected route, rather than assumed to match ours.
We plan to distinguish request metadata from stored prompt and output content, with stated retention and deletion options. Zero-retention options would require verified support across the selected processing path.
Match the deployment to your security and compliance requirements, with access, backups, support, and contractual commitments reviewed together. Inference, account, and billing records each have their own location and handling terms.
Our facility planning prioritizes efficient operations and verifiable clean-electricity procurement, with energy claims tied to evidence you can review.
These are design and procurement goals. Facility energy use, electricity sourcing, and environmental reporting will depend on the final site and operating arrangements.

We plan to validate model access and customer workloads with teams in Canada and the U.S., using approved capacity as the service and facility plans develop.
Evaluate request compatibility, model capabilities, routing policies, usage metering, and the needs of Figena, Cilila AI, and independent API customers.
Plan limited workloads with selected customers on approved owned or partner capacity, with clear limits, data terms, billing, and support arrangements.
Expand model choices and dedicated capacity with customer needs in both markets, guided by operating experience and confirmed capacity requirements.
The 2028–2029 target planning window concerns the initial facility. API pilots and facility development can progress in stages, with access dates and deployment locations announced separately as they are confirmed.
Connect this capability with the tools your business needs next.