StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Home
  2. Companies
  3. primer.io
primer.io

primer.io

Remoteprimer.io

Primer consolidates your payments stack with a unified API, and supercharges your checkout with data driven insights.

54tools
1decisions
0followers
OverviewTech Stack54Dev Feed

Tech Stack

View all 54
Stack by Layer
Application & Data27
Utilities9
DevOps14
Business Tools4
Application & Data
27 tools (50%)
Utilities
9 tools (17%)
DevOps
14 tools (26%)
Business Tools
4 tools (7%)

Application & Data

27
dbtCockroachDBPythonDocker ComposeAmazon AuroraAmazon DynamoDBAmazon EKSZoomRedisKubernetesHelmAmazon CloudFrontAWS Elastic Load Balancing (ELB)Amazon S3AWS LambdaAWS Elastic BeanstalkDockerAmazon Route 53FastAPITypeScriptPostgreSQLAWS Database Migration ServiceFirebaseServerlessJavaScriptSnowflakeElastic Cloud

Utilities

9
Amazon KinesisAmazon SQSSlackAmazon API GatewayAWS WAFAWS Key Management ServiceAmazon Kinesis FirehoseAWS Certificate ManagerAmplitude

DevOps

14
GitHubTerraformDatadogJiraFluentdAmazon GuardDutybehaveAWS CloudTrailWebpackSentryCypressBrowserStackGitLab CIJenkins

Business Tools

4
FigmaStorybookReactNotion

Latest from Engineering

View all
Matthew Evans
Matthew Evans

Aug 5, 2020

DecidedonRedisRedisMemcachedMemcached

The obvious volatile memory choices were either Memcached or Redis. We eventually sided with Redis as it natively handled replication, and this replication fell under the PCI responsibility scope of AWS. This added duribility meant that if a redis node were to die, our downtime would be in the seconds, rather than 15 minutes which we would incur using Memcached

30.2k views30.2k
Comments

Team on StackShare

3
Will Knowles
Matthew Evans
Alex Bernard