No session logs
Prompts and outputs are not retained, and are not used to train or fine-tune OneNexus models.
Pilot & Security
What your security review needs to know
Pilot terms, data handling, network model, and support — on one page. If a fact is not here, ask rather than assume it.
The pilot at a glance
| Availability | Internal teams within One Mount Group and Techcombank. External teams can register interest, and we will let them know when external access opens. |
|---|---|
| Duration | Typically 4–6 weeks, agreed at kickoff. |
| Cost | Free during the pilot. |
| Response time | Acknowledgement within one business day. |
| Next step | After the success review, production availability, capacity, and commercial terms are assessed separately. |
How onboarding works
- Submit the request.
- Confirm use case and data classification.
- Get workspace, quota, and credentials.
- Run the quickstart.
- Review success criteria with us.
How pilot data is handled
Tenant isolation by design
Workspaces, API keys, quotas, data, and usage records are scoped to your organisation.
Encryption in transit
All API and console traffic is served over TLS.
Network access model
The inference endpoint is public over TLS, gated by credentials rather than network location: a tenant-scoped API key is what grants access, so no VPN or allow-listing is required.
Requests without a valid key are rejected — reaching the endpoint grants nothing.
Support and incidents
- Support hours
- Working hours, 9:00 - 18:00 (GMT+7), Monday to Friday.
- Incident contact
- Your named onboarding contact — the same people who issued your workspace and keys.
- Service commitment
- Capacity is shared and quotas are fixed. Incidents are worked during support hours.