Delivery Artifacts
Delivery Artifacts
This page describes the components delivered as part of the SMS Gateway Proxy platform and the versioning policy.
Platform Components
| Component | Image | Version | Description |
|---|---|---|---|
| SMPP Proxy | sms-sender-proxy | v1.0.0 | Core messaging gateway — SMPP routing, rate limiting, delivery tracking, REST & gRPC APIs |
| MCP | node-red (custom flows) | v1.0.0 | Message Control Platform — contact policy enforcement, deduplication, blacklisting |
| Redis | redis:latest | — | Distributed rate limiting and MCP state storage |
| Aerospike | aerospike:ce-6.4.0 | — | Message lifecycle state persistence |
| MinIO (optional) | minio | — | S3-compatible storage for journal export and blacklist files |
Versioning Policy
The platform follows Semantic Versioning (SemVer):
- Major version — breaking changes to API contracts or configuration format
- Minor version — new features, backward-compatible
- Patch version — bug fixes, performance improvements
All platform components within a release are tested and validated together. It is recommended to deploy matching versions of the Proxy and MCP components.
Configuration Artifacts
In addition to Docker images, the deployment includes:
| Artifact | Format | Description |
|---|---|---|
smpp_rules.toml | TOML | SMPP link and pool configuration |
routes.ini | INI | Routing rules for message filtering per link |
| MCP flows | Node-RED JSON | Contact policy flow definitions |
Next Steps
- Installation Guide — deploy the platform
- Configuration Reference — configure SMPP links and pools
- Infrastructure — component architecture overview