Skip to content

CRM IN — Twenty CRM

Twenty CRM instance for the India operation at in.crm.eidos-global.com. ~1 user today. Same product and same E2 host as CRM UK and CRM TnE — separate Twenty container + Postgres for tenant isolation.

Field Value
Public URL https://in.crm.eidos-global.com
Audience India sales / leadership (~1 user)
Criticality medium — strategically important, low daily-usage volume
Maturity hobby/trial
Owner [INFO NEEDED]
Last reviewed 2026-05-07

1. At a glance

Twenty CRM (open-source) running on Dokploy on E2. India sales operates a separate CRM instance from UK — likely for organisational separation (different team / sales territory) rather than data-residency, since the host is in uk-london-1 not in India.

Operationally near-identical to CRM UK and CRM TnE — same image, same Dokploy setup, same shared SMTP credential, same backup posture.

2. Business purpose

Pipeline visibility for India sales / leadership.

3. Audience

India sales / leadership team. ~1 user today.

4. Hosting & cloud infrastructure

  • Server: E2 EIDOSDev1 Dokploy VPS (145.241.230.130)
  • Deploy method: Dokploy
  • Reverse proxy: Caddy on E1 → Dokploy/Traefik on E2 → Twenty container

Infrastructure map

Item Value Notes
Public hostname in.crm.eidos-global.com DNS via E1 Caddy → E2
Backend host E2 (Dokploy) shared with 8 other apps
Twenty CRM image tag :latest not pinned
Database dedicated PostgreSQL container (separate from CRM UK / TnE)
File uploads / attachments local disk on E2 not in MinIO
Region of data uk-london-1 (UK) despite "IN" branding — [CONFIRM] whether this is acceptable under India DPDP Act for the data being processed
TLS cert Caddy auto-LE

Credentials in Vault

Secret type Vault location
Twenty workspace admin [INFO NEEDED]
Postgres password [INFO NEEDED]
App secret / signing key [INFO NEEDED]
SMTP credentials kv_pe/OCI-SMTP — shared across the estate

5. Technology behind it

Same as CRM UK §5 — Twenty CRM container on Dokploy, image on :latest, dedicated Postgres.

6. Data it handles

  • Customer / prospect contact details for India market
  • Pipeline / deal information
  • Few records today (early stage)

DPDP Act / data-residency: server in uk-london-1 while serving India operations — worth confirming this complies with the Indian Digital Personal Data Protection Act for the kinds of records being held. At 1 user and minimal data this is below practical concern; revisit before significant volume.

7. External dependencies

Same as CRM UK.

8. Authentication & access

Same email-magic-link pattern as the sister CRMs — see CRM UK §8. Same M365-MFA-as-the-effective-MFA story.

9. Maturity assessment

Same shape as CRM UK §9.

10. Known risks & vulnerabilities

  • Cross-border data flow concern — if records ever sync between UK / IN CRMs, that's a transfer event under DPDP Act. Currently no integration exists, so no flow today.
  • All other risks shared with CRM UK: untested backup, local-disk uploads, image-on-:latest, no GDPR posture, magic-link auth, shared SMTP cred.

11. Impact if it goes down

  • 1 India user blocked from pipeline.
  • Negligible immediate impact at current usage.

12. Owner & on-call

[INFO NEEDED]

13. References & links