Cloudflare
Workers and D1 in the current RACAI backend/runtime; the commercial website has a separate Sites release path.
Current infrastructure · not a partnershipRACAI / Engineering reality
TECHNOLOGY
WITH A JOB
TO DO.
Tools matter only when they make something reliable, useful and measurable. Here is what we operate now, what we have engineered before and what is considered per project.
Explore the stack01 / In current RACAI systems
Platform experience · operational recordsCurrent foundations.
Platforms with current RACAI use documented in our operating repository and release work. Product availability and production acceptance are tracked individually.
GitHub
Private source control, reviewed branches, pull requests, traceability, recovery and automation workflows.
Current tool · not endorsementResend
Verified-domain mail sending/receiving and inbox workflows; delivery claims are scoped to observed tests.
Current provider integrationGA4 & Clarity
Consent-gated traffic and interaction measurement. Masking, CSP/security boundaries and live acceptance are explicit release controls.
Configured measurement tools · privacy-gatedTelegram
Bot workflows, event tracking and human approval interfaces connected to internal systems.
Current interface / controlled automationJavaScript & SQL
Service logic, APIs, tests, state handling, structured data and integrations.
Demonstrated engineering capabilities02 / Previously engineered
Historical experience · not current hostingExperience beyond
today's deployment.
RACAI previously used a more traditional infrastructure model. We retain that engineering experience without pretending the retired server is still running.
Amazon Web Services (AWS)
Prior use of Amazon EC2 for server-hosted application operations. RACAI's current operating model is Cloudflare-first; this is not a claim of AWS Partner status or current AWS hosting.
Node.js · Express · PostgreSQL · Redis
API services, relational schemas, queues and operational state in earlier RACAI/Control-Room systems.
nginx · PM2 · job queues
Traditional server processes, reverse proxies, background execution, monitoring and recovery concepts.
03 / Engineering principles
Client-first implementationChoose the stack
for the problem.
Security before speed.
Least-privilege credentials, source traceability, consent checks and rollback plans.
Durability over demos.
Real inbound receipts, tests, observable behavior and clear human ownership.
Costs tied to value.
Minimal infrastructure and no unsupported promises of zero cost at enterprise scale.
About the technology names on this page.
Explore what we build These are factual references to tools and technologies. Their respective trademarks belong to their owners. The use of names does not imply endorsement, certification, reseller status or a commercial partnership. Official logos, badges and co-branded assets are not used without a specific permitted use or license.