Skip to content

CRM TnE Connect — Twenty CRM

Twenty CRM instance for the TnE Connect product business unit at crm.tneconnect.app. ~3 users — the largest of the three CRMs. Same Twenty-on-Dokploy pattern as CRM UK and CRM IN.

Field Value
Public URL https://crm.tneconnect.app
Audience TnE Connect sales / customer-success (~3 users)
Criticality medium — supports the TnE Connect SaaS go-to-market
Maturity hobby/trial
Owner [INFO NEEDED]
Last reviewed 2026-05-07

1. At a glance

Twenty CRM (open-source) for the TnE Connect product business unit. ~3 users today. Tracks prospective customers + active accounts (Fourway, prospects from the recently-relaunched tneconnect.app marketing site, RocketSaas-driven leads).

Strategically the most important of the three CRMs, since the company is betting on TnE Connect as a growth product.

2. Business purpose

  • Sales pipeline + customer-success for the TnE Connect SaaS.
  • Leads from the tneconnect.app marketing site land here.
  • Account view of paying customers (Fourway today; future tenants).

3. Audience

TnE Connect business unit (sales + CS staff). ~3 users 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 crm.tneconnect.app .app TLD = HSTS-preloaded → HTTPS mandatory
Backend host E2 (Dokploy) shared with 8 other apps
Twenty CRM image tag :latest not pinned
Database dedicated PostgreSQL container (separate from CRM UK / IN)
File uploads / attachments local disk on E2 not in MinIO
TLS cert Caddy auto-LE must not lapse — HSTS preload = no fallback

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.

6. Data it handles

  • TnE Connect prospect / customer contact details
  • Possibly contract terms, billing references for paying tenants like Fourway
  • Trial sign-up captures from the marketing site

GDPR scope if this captures EU/UK leads at scale. Today small enough to be below the practical threshold; revisit as RocketSaas-driven inbound starts to build a real funnel.

7. External dependencies

  • E2 host availability
  • Oracle Email Delivery (shared SMTP)
  • tneconnect.app WordPress (the marketing site that should feed leads here — [INFO NEEDED] whether the wiring exists today)

8. Authentication & access

Same email-magic-link pattern as sister CRMs — see CRM UK §8.

9. Maturity assessment

Same shape as CRM UK §9.

10. Known risks & vulnerabilities

  • .app TLD HSTS-preload — TLS lapse is catastrophic.
  • Marketing-funnel breakage hidden — if the tneconnect.app WordPress sends leads here and the wiring breaks, leads vanish silently. Worth a synthetic test (RM-038 extension).
  • All other risks shared with CRM UK: untested backup, local-disk uploads, image-on-:latest, magic-link auth, shared SMTP cred.

11. Impact if it goes down

  • 3 TnE Connect business-unit users blocked from pipeline.
  • Trial-onboarding funnel may stall if the WordPress marketing site is wired to push leads here.
  • Strategic visibility loss as the SaaS go-to-market scales.

12. Owner & on-call

[INFO NEEDED]

13. References & links