Why we’re changing our product from an API to a Linux service

At SafeTalpa we have been showing our product to merchants of all sizes during the last few weeks. The algorithms that we packed into single lines of code to help these companies maintain PCI compliance are really good, I can say that we’ve finally built something that a few people love a lot.

After speaking with these companies we’re making our product even easier to use. We’re now building a product with more possibilities and fewer limitations. Here’s why we decided to make this change:

1. With a Linux service, the user won’t have to touch its codebase.
2. We’ll be able to do internal corrections to the infrastructure of the merchant, such as closing ports that shouldn’t be open, programmatically.
3. We won’t have to build an SDK for every single relevant programming language. Which means we’ll be able to deploy new features faster.
4. Sending system logs out of the merchant’s infrastructure to our infrastructure was sketchy. With this new solution, those logs won’t leave their infrastructure.
5. The pricing structure is even simpler now.
6. This change is pretty much a copy-paste of our existing algorithms. We’ll be able to re-use approximately 90% of our existing code.

Achieving product-market fit is the goal and it’s one that takes long.