Kitlore
Multi-tenant headless CMS prototype with asynchronous AI-assisted publishing workflows.
- Type
- SaaS
- Client
- Independent headless CMS prototype
- Role
- Backend architecture · Product engineering
- Year
- 2025
Evidence / status
Prototype. Reported outcomes await verification.
Challenge
A secure multi-tenant publishing pipeline
The prototype needed to isolate customer data, protect credentials, and keep slow generation work out of synchronous API requests.
Constraints
- Tenant records needed strict isolation.
- API keys could not be stored in plaintext.
- Generation jobs could take several seconds.
- Webhook delivery needed integrity checks and retry support.
Approach
Key decisions
Concurrent Go services
Go and Gin provide a typed service layer for concurrent request and job handling.
Queue-backed generation
Redis-backed jobs separate request acknowledgement from content generation and delivery.
Tenant-aware repositories
Tenant identifiers are included at the repository boundary for every relevant data operation.
Hashed and encrypted credentials
API keys are hashed, OAuth tokens are encrypted, and webhook payloads are signed.
Evidence
What can be stated
Current status: Prototype. Unverified outcomes are labelled instead of presented as proof.
- Review source (opens in a new tab)
Security and response-time claims can be reviewed in the linked repository but are not independently verified.
Needs verification
Technology stack
- Go
- Next.js
- PostgreSQL
- Redis
Next project
Continue through the work archive.
Start a project
Let's build something great
Drop your details below. We'll have it open in Gmail, ready to send — no copy-pasting.