Product and runtime
Pejot Solutions
AuroraTabs, the licensing runtime, local protected cache, and the product experience around research tabulation workflows.
Partner story · AuroraTabs × MAD Services
Partners who keep research tools ready for work.
For AuroraTabs, Pejot Solutions built a self-hosted Keygate licensing layer. MAD Services operates the AWS foundation designed to keep verification available without getting in the way of daily table and reporting work.
Collaboration
A shared responsibility model for a desktop product.
AuroraTabs supports research teams working with JOB and VAR files, calculations, table previews, and Excel exports. The licensing layer must protect the product without becoming another point of friction in that workflow.
A licence should protect the product, not stand between a user and their work.
Managed AWS foundation
MAD Services
Cloud infrastructure, observability, and operational care for the AWS layer supporting licence verification.
Service targets
Availability translated into a measurable operating standard.
Target monthly availability for the licensing service.
SLI: successful licensing endpoint responsesTarget time to resolve an incident that affects service continuity.
SLA target for operational incidentsControlled offline working period after a prior successful activation.
Offline grace targetLicensing design
Self-hosted licensing with the sensitive parts kept server-side.
Self-hosted Keygate
Keys, activations, and licence status are managed in dedicated infrastructure rather than through a third-party licensing SaaS.
Device-bound activation
On first launch, AuroraTabs verifies a licence key and associates it with a technical machine identifier.
Windows DPAPI protected cache
Local licence state is protected for the current Windows user; it is not a plain key file.
Server-side secret handling
The reverse proxy applies the internal authorisation header, so the primary Keygate API key does not sit in the desktop application.
Continuity
Designed for the failure case, not only the ideal day.
The AWS design uses an Application Load Balancer, two ECS Fargate availability zones, and RDS PostgreSQL in a Multi-AZ configuration. Health checks and deployment safeguards are intended to limit the impact of an unhealthy task or failed release.
AuroraTabs first refreshes the licence online. If the service or connection is temporarily unavailable, the protected cache is designed to keep the desktop application available within a controlled offline grace period.
1
ALB and WAFProtected HTTPS entry point and traffic control.
2
Two ECS Fargate zonesService placement across two availability zones.
3
RDS Multi-AZSynchronous standby and automated failover capability.
4
Monitoring and backupsOperational telemetry, backups, and response processes.
Outcome
Licensing stays in the background. AuroraTabs stays in focus.
Licence verification and status refresh at subsequent launches.
Controlled continuity through protected local state and an offline grace period.
A safe way to disconnect a machine before moving a licence.
Architecture ready for shared seats through checkout and heartbeat workflows.