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. Karma
Karma

Karma

new york, nyyourkarma.com

Karma Go lets you take WiFi everywhere. Pay-as-you-go for data that never expires. No contracts or monthly fees. With nationwide coverage on LTE, stay connected to the internet with all of your devices, seamlessly.

44tools
10decisions
6followers
OverviewTech Stack44Dev Feed

Tech Stack

View all 44
Stack by Layer
Application & Data25
Utilities7
DevOps8
Business Tools4
Application & Data
25 tools (57%)
Utilities
7 tools (16%)
DevOps
8 tools (18%)
Business Tools
4 tools (9%)

Application & Data

25
UnicornAmazon Route 53Amazon RDSVagrantGoogle DriveAmazon S3DropboxMySQLAmazon EC2NGINXRubyAmazon CloudFrontAmazon VPCPowSinatraGolangAmazon DynamoDBRailsBootstrapSassJavaScriptCoffeeScriptJavaObjective-CAndroid SDK

Utilities

7
MandrillStripeGoogle AnalyticsSlackCoinbaseAmazon SQSAmazon SNS

DevOps

8
ChefSentryVimGitTravis CIGitHubNew RelicXcode

Business Tools

4
MailchimpiDoneThisG SuitejQuery

Latest from Engineering

View all
Stefan Borsje
Stefan Borsje

Jan 15, 2015

Needs advice

Pow is what we use for development on our local machines. It's easy to setup, and easy to maintain since it also eliminates the need for maintaining a /etc/hosts file. Pow

3.23k views3.23k
Comments
Stefan Borsje
Stefan Borsje

Jan 15, 2015

Needs advice

We use Bootstrap a lot. Everything that you see on our marketing website or web servers, it's all built from Bootstrap. Bootstrap

261 views261
Comments
Stefan Borsje
Stefan Borsje

Jan 15, 2015

Needs advice

We use Rails for webpages and projects, not for backend services. Actually if you click through our website, you won't notice it but you're clicking though, I think, seven or eight different Rails projects. We tie those all together with a front-end library that we wrote, which basically makes sure that you have a consistent experience over all these different Rails apps.

It's a gem, we call it Karmeleon. It's not a gem that we released. It's an internal gem. Basically what it does is it makes sure that we have a consistent layout across multiple Rails apps. Then we can share stuff like a menu bar or footer or that kind of stuff.

So if we start a new front end project it's always a Rails application. We pull in the Karmeleon gem with all our styling stuff and then basically the application is almost ready to be deployed. That would be an empty page, but you would still have top bar, footer, you have some custom components that you can immediately use. So it kind of bootstraps our entire project to be a front end project. Rails

382 views382
Comments
Stefan Borsje
Stefan Borsje

Jan 15, 2015

Needs advice

In the beginning we thought we wanted to start using something like RabbitMQ or maybe Kafka or maybe ActiveMQ. Back then we only had a few developers and no ops people. That has changed now, but we didn't really look forward to setting up a queuing cluster and making sure that all works.

What we did instead was we looked at what services Amazon offers to see if we can use those to build our own messaging system within those services. That's basically what we did. We wrote some clients in Ruby that can basically do the entire orchestration for us, and we run all our messaging on both SNS and SQS. Basically what you can do in Amazon services is you can use Amazon Simple Notification Service, so SNS, for creating topics and you can use queues to subscribe to these topics. That's basically all you need for a messaging system. You don't have to worry about scalability at all. That's what really appealed to us. Amazon SQS

431 views431
Comments

Team on StackShare

1
Stefan Borsje