# Dedicated instances

Your own Texa Desk, on servers in your country, on your own domains, run by Texa.


A dedicated instance is a complete Texa Desk for one company: its own Texa Desk, service layer,
databases, files and backups, on servers in the country it chooses, under its own domains. Texa
runs and updates it. Ask [info@texadesk.com](mailto:info@texadesk.com) to plan one.

## What changes for developers

Nothing in the APIs. The same routes and SDKs work; only the addresses are yours:

| | Texa's hosting | Your instance (say `pilotbank.ng`) |
|---|---|---|
| Texa Desk and its API | `https://desk.texadesk.com` | `https://desk.pilotbank.ng` |
| Texa API | `https://api.texadesk.com` | `https://api.pilotbank.ng` |
| Webhooks into Texa | `https://hooks.texadesk.com` | `https://hooks.pilotbank.ng` |
| Voice sessions | `wss://voice.texadesk.com` | `wss://voice.pilotbank.ng` |
| The Texa Relay | given per company | `relay.pilotbank.ng` |

Point the SDKs at your address:

<!-- tabs -->
```python Python
texa = Client(base_url="https://api.pilotbank.ng")
```
```js JavaScript
const texa = new TexaClient({ key: process.env.TEXA_API_KEY!, baseUrl: "https://api.pilotbank.ng" });
```
```go Go
c, _ := texa.New("", "https://api.pilotbank.ng")
```
<!-- /tabs -->

## Only on a dedicated instance

- **The [Platform API](/api-reference/platform):** create accounts, people and agent bots across the
  whole instance, with a platform app's token from the instance's super admin.
- **Your own sign-in rules** for the whole instance, and its own audit trail.

## Texa AI on a dedicated instance

Texa AI's engine and its models can run for the instance in the same country, on request. Until
they do, the instance's **Texa AI → Safety** page says where they run, so your compliance team sees
it plainly.