TICAMAC Group

The digital ecosystem of my technology group

I founded TICAMAC Group in Douala and I build its entire digital ecosystem: the division websites, the CMS, the AI assistant, the e-signature platform, the infrastructure that hosts them and the brand identity that ties it all together.

ticamac.com home page: “Building a smarter tomorrow.”
Sheet
01 · TICAMAC Group
Period
Sept. 2025 → today
Status
In productionIn development
Role
Founder · products, development, infrastructure, identity
Technology
Next.js 16 · React 19 · TypeScript · Payload CMS 3 · PostgreSQL 16 · Turborepo · Docker Compose · Nginx · Cloudflare Tunnel · GitHub Actions · Umami · Remotion
Revision
v1 live since 22 Sept. 2026 · V2 in development
Sheet 01.0

The project in motion

TICAMAC Group · the project in motionOct 6, 2026 · MP4 · 1.2 MB
Transcript

15-second film, no voice or music. Title “TICAMAC Group”, then a frame draws itself and real screenshots of the project follow inside it; below, the layers I worked on light up. It ends on the project's address.

Sheet 01.1

One group, one platform

TICAMAC Group is organised in divisions: training with TICAMAC Academy, software development with TICAMAC Software, coworking with TICAMAC Hub. Others will follow. Instead of building a separate website for each division, I built a single platform that runs them all, with the same CMS and the same components.

PUBLIC SITES · IN PRODUCTIONGroupticamac.comAcademyacademy.Softwaresoftware.Hubhub.Blogblog.AIbetaSHARED PLATFORM · CMS · DESIGN SYSTEM · SERVERCMSPayloadSigne-signatureAnalyticsUmamiCloudNextcloudInvestin developmentPRIVATE SERVICES · RESTRICTED ACCESSUPCOMING DIVISIONSCloudin preparation · 2027Infrastructurein preparation · 2027EnergyplannedLabsplannedVenturesplannedNot launched yet.
What is live, what is private and what is in preparation, as of 6 Oct. 2026.
Sheet 01.2

A brand that holds up everywhere

Before writing any code, I set the identity down in brand guidelines (v2.0, March 2026): an isotype shaped like a map of Africa with a connection node, a logo for each subsidiary, the colours, usage rules, social media formats, the email signature and the letterhead.

TICAMAC Group main logo, stacked version
Main logo
TICAMAC Group wordmark
Group wordmark
TICAMAC isotype: the map of Africa and its connection node
Isotype
TICAMAC isotype in gold
Gold isotype
TICAMAC wordmark in monochrome
Monochrome
TICAMAC Group logo
Group
TICAMAC Academy logo
Academy
TICAMAC Software logo
Software
TICAMAC Cloud logo
Cloud
TICAMAC Labs logo
Labs
TICAMAC Energy logo
Energy
TICAMAC Ventures logo
Ventures
Colours
Navy Deep #0F2137, Tech Blue #1A6BB5 and Prestige Gold #D4A745. On the web, each division keeps its own colour: green for Academy, purple for Software, orange for Hub.
Rules
Clear space, minimum sizes and forbidden uses: no stretching, no rotating, no shadow, no low contrast.
Media
Letterhead, email signature, LinkedIn and Facebook banners, share image, WhatsApp Business cover.
TICAMAC LinkedIn banner
LinkedIn banner from the brand guidelines.
Sheet 01.3

Eight applications in one repository

The code lives in a monorepo: seven Next.js applications (Group, Academy, Software, Hub, Blog, AI, Invest) and a Payload CMS. They share the same components, brand and configuration, so I can fix something once for every site.

  • If the CMS goes down, the sites stay online: each one keeps fallback data.
  • A contact or quote request is saved before the email goes out, so none gets lost.
  • Forms are limited to five submissions per hour, without storing visitors' IP addresses.
  • Newsletter with double opt-in, page drafts and preview before publishing.
  • The AI assistant keeps its keys on the server and stores no conversation.
Full ticamac.com home page
Captured on Oct 6, 2026
Sheet 01.4

Hosted on my own server

Everything runs on my own Ubuntu server. No port is open to the Internet: traffic goes through a Cloudflare tunnel, reaches Nginx, then the Docker containers. The PostgreSQL database is only reachable from the internal network.

VisitorHTTPSCloudflareDNS · TLS · cachetunnelMY UBUNTU SERVER · NO INBOUND PORT OPENcloudflaredsystemd · outboundNginxlocal onlyDOCKER CONTAINERSGroupAcademySoftwareHubBlogAIInvestCMSUmamiPostgreSQLinternal networkBackupsdaily dumps · media · restore
Simplified diagram: real addresses, identifiers and ports are not published.
Deployment
Before each release, a script checks the server, takes a backup, restarts the services and tests the sites.
Backups
Database and media backed up daily, with restore scripts kept next to the code.
CI/CD
GitHub Actions checks every change (lint, types, build) before deployment.
Analytics
Umami, which I host myself, cookieless.

◆ Note22 September 2026. On the first release, six out of seven services refused to start. I found the cause (a read-only file system), shipped the fix the same day and wrote down what was left to sort out.

Sheet 01.5

V2, step by step

For V2, I have two AIs working in the same pull request: Claude writes the code, ChatGPT reviews it and gives written feedback, then I sign off before moving to the next step. It looks slower on paper, but I fix far less afterwards.

  • Each site (Group, Academy, Software, Hub, Blog) moves to pages built in the CMS, with drafts and preview.
  • A shared security baseline: strict content security policy, limited CORS, login rate limiting, security tests on the CMS.
  • Drafts stay invisible to the public, and tests check it.
Sheet 01.6

The brand in motion

I also animate the brand in code, with Remotion: intro, outro, division branding, titles and transitions. Colours and proportions come straight from the brand guidelines.

TICAMAC · brand introSep 30, 2026 · MP4 · 130 KB
Transcript

On a navy background, the Africa-shaped isotype appears, the connection node lights up, then the TICAMAC wordmark writes itself alongside. No voice, no music.

Contact sheet of the animated TICAMAC division branding
Animated division branding, frame by frame.
Sheet 01.7

Before the platform

In December 2025, TICAMAC was a single Next.js site, with animations and placeholder statistics. Nine months later, the brand runs on a multi-site platform that I host and keep improving. In between, I also prototyped TICAMAC SOS, a school management demo.

ticamac.com home page: “Building a smarter tomorrow.”
TICAMAC website from December 2025, replayed from the archive
Dec. 2025Sept. 2026
The 2025 version was relaunched from my archives, then captured on 6 Oct. 2026.
TICAMAC SOS demo start screen, a school management system
TICAMAC SOS, school management demo (2026). Prototype, never sold.
Sheet 01.8

How I built it

Cédric
  • Group and division structure
  • Brand direction
  • Architecture, sign-off, deployment
  • Server, DNS, operations
Claude
  • Development of the monorepo, CMS and sites
  • Deployment and backup scripts
  • Remotion animations
ChatGPT
  • Architecture and planning
  • Review of V2 steps

What I take away

  • A site should not go down because its CMS does.
  • A backup you have never restored is not worth much.
  • Moving in small reviewed steps is faster than fixing one big delivery.

Online

These addresses were responding on Oct 7, 2026.