Signal-Based Secure Platform via Go Microservices

I need a full, production-ready fork of the open-source Signal project, re-architected as a set of container-friendly Go microservices. The goal is to keep the rock-solid end-to-end encryption that Signal offers while gaining the flexibility, horizontal scalability, and deployment speed that a Go-driven service mesh provides.

Project Overview
We are building a next-generation secure communication platform based on the open-source Signal ecosystem. Our goal is to create a production-ready platform that supports millions of users while preserving Signal's proven end-to-end encryption. We are looking for senior engineers with experience in distributed systems, Go, Java, cloud infrastructure, and large-scale backend development.

Technology Stack
• Signal Server (Fork) and libsignal
• Go for all new microservices
• Java for the existing Signal Core
• Python for AI-related services only
• ScyllaDB (messaging storage strategy)
• PostgreSQL (business/platform data)
• Redis
• NATS JetStream
• gRPC + REST APIs
• Docker + Kubernetes

Project Scope
• Secure messaging platform
• Voice & video calling
• Business platform
• Commerce modules
• Verification system
• Education Result Platform (independent backend)
• Admin panel and business portal
• High-performance APIs

Responsibilities
• Understand existing Signal architecture
• Implement scalable Go microservices
• Design production-grade APIs
• Write clean, documented, tested code
• Participate in architecture reviews
• Optimize latency, memory usage and scalability
• Follow secure coding practices

Required Skills
• Go (expert)
• Java/Spring ecosystem (good understanding)
• Distributed systems
• gRPC
• REST API design
• ScyllaDB experience
• PostgreSQL
• Redis
• Docker
• Kubernetes
• Git
• CI/CD

Nice to Have
• Signal ecosystem experience
• End-to-end encryption knowledge
• Large-scale messaging systems
• WebRTC
• OpenTelemetry
• Prometheus/Grafana

Application Requirements
• Relevant GitHub profile
• Links to production systems
• Architecture experience
• Examples of scalable backend work
• Availability
• Expected hourly rate or fixed-price estimate


Core work includes:
• Forking Signal’s client/server code and refactoring the server side into discrete Go services for messaging, key exchange, presence, media relay, and push notifications
• Exposing clean REST or gRPC APIs with comprehensive Swagger/Proto documentation
• Delivering Docker images and a simple Kubernetes or Docker-Compose orchestration file so the stack spins up with a single command
• Supplying a minimal reference client (CLI or bare-bones web) that demonstrates account creation, secure one-to-one chat, and group chat over the new services
• Writing unit and integration tests that cover cryptography, authentication flows, and message delivery guarantees
• Providing a short deployment guide and inline code comments for ongoing maintenance

Acceptance criteria: all messages must be encrypted end-to-end using the Signal protocol; test suite passes in CI; containers build reproducibly; a demo conversation between two accounts works out of the box.

Preferred tech: Go 1.21+, ScyllaDB, PostgreSQL, Redis, gRPC/REST, Docker, Kubernetes (optional), GitHub Actions or similar CI.

I will review milestones on live, running containers—no screenshots—so the deliverable must be runnable on a fresh cloud VM.