Services
Coralogix
Rationale Coralogix is Fluid Attacks' main observability tool. The main reasons why we chose it over other alternatives are the following: It provides a granular (per-GB) consumption pricing model, which scales perfectly on horizontal-based ...
Pluralsight Flow
Rationale Pluralsight Flow is Fluid Attacks' tool for gaining insights into the development process, both individually and collectively. The main reasons we chose it over other alternatives are: It integrates with GitLab, the platform we use to ...
Jamf
Rationale Jamf is Fluid Attacks' MDM system. The main reasons why we chose it over other alternatives are the following: It focuses on macOS and iOS devices. It supports Apple Business, critical for being able to maintain full control of devices. It ...
dbt
Rationale dbt is Fluid Attacks' tool for data transformation, documentation, and integrated testing. The main reasons why we chose it over other alternatives are: It does not tie us to any BI provider. It works seamlessly across multiple database ...
QuickSight
Rationale QuickSight is our tool for dashboarding and reporting. The main reasons why we chose it over other alternatives are: It is fast at querying and graphing. It is easy to use, with a traditional drag-and-drop structure. It follows a ...
Snowflake
Rationale Snowflake is our database for analytical purposes. The main reasons why we chose it over other alternatives are: It is much faster. It has a deeper Terraform integration. It offers flexible permission sets. It integrates well with dbt. It ...
Zoho One
Rationale Zoho One is Fluid Attacks' CRM, used for many company-critical processes like Sales, Marketing, Finance, Human Resources, etc. The main reasons why we chose it over other alternatives are: It is an all-in-one solution that allows ...
Google Workspace
Rationale Google Workspace is Fluid Attacks' main productivity and collaboration tool. The main reasons why we chose it over other alternatives are the following: It is an all-in-one solution that provides many essential features like email, ...
Ubiquiti
Rationale Ubiquiti EdgeRouter 8 is the router we mainly use to create VPN tunnels with some clients, and for direct access with some clients via MPLS. Usage We use Ubiquiti to establish VPN connection with some clients Guidelines In order to ...
Statuspage
Rationale Statuspage is our main communication tool with users regarding our product's health and incidents. This helps us inform quickly, clearly, and transparently about outages, performance degradations, or any other eventuality in our components ...
Okta
Rationale Okta is the IAM platform we use for managing access to hundreds of applications used across our company. It allows us to give access to applications without disclosing credentials and maintaining a least privilege approach. The main reasons ...
LogRocket
Rationale We use LogRocket as one of our error-tracking tools. It allows us to get data-sanitized insights into user actions, error codes, requests, responses, and more by recording users' screens, making it easy to reproduce problems. With filters ...
GitLab CI
Rationale GitLab CI is the system that orchestrates all the CI/CD workflows within our company. Such workflows are the backbone of our entire development cycle. By using it, we become capable of: Running automated processes on every commit ...
GitLab
Rationale GitLab is the platform we use for developing our software. It provides essential services like Git repositories, Merge requests, Development planning, CI/CD, among many others. The main reasons why we chose GitLab over other alternatives ...
Cloudflare
Rationale Cloudflare is our SaaS provider for some infrastructure solutions like DNSSEC, DDoS Protection, Rate limiting, Auto-Renewable SSL certificates, Content delivery network, Web Application Firewall, Anti-bot capabilities, Zero Trust Network ...
Checkly
Rationale Checkly is our monitoring-as-code (MAC) tool for check-based tracking across our products. As a pivotal part of our continuous monitoring strategy, Checkly allows us to define and manage periodical testing for each one of our components to ...
VPN
Rationale VPN (Virtual Private Network) is the cloud-based solution for virtual private networks we use. The main reasons why we chose it over other alternatives are the following: It allows us to connect to our client private networks in a ...
VPC
Rationale We use AWS VPC (Virtual Private Cloud) for hosting our own private network in the cloud. It allows us to manage network configurations like subnets, IP addressing, Internet gateways, Routing tables, Security groups, among others. The main ...
SageMaker
Rationale SageMaker is the platform we use for developing solutions involving Machine Learning. The main reasons why we chose it over other alternatives are: It integrates with EC2, allowing to easily provision cloud computing resources. Such feature ...
S3
Rationale AWS S3 (Cloud Object Storage) is the service we use for storing files in the cloud. The main reasons why we chose it over other alternatives are: It is SaaS oriented, meaning that in order to start storing data, we only need to create a ...
OpenSearch
Rationale OpenSearch is an open-source search engine forked from ElasticSearch that came as a response to some licensing issues Amazon had with Elastic, the original developers. It is maintained by AWS and a community of developers. It enables ...
Lambda
Rationale Lambda is the service we use for running serverless functions. The main reasons why we chose it over other alternatives are the following: It allows us to execute tasks without having to design any infrastructure. It complies with several ...
KMS
Rationale AWS KMS (Key Management Service) is the service we use for storing and using cryptographic keys. It allows us to have non-readable symmetric and asymmetric private keys hosted in the cloud. The main reasons why we chose it over other ...
IAM
Rationale AWS IAM (Identity and Access Management) is the core AWS service for managing authentication and authorization within the platform. It allows us to have least privilege compliance regarding resource access. The main reasons why we chose it ...
ELB
Rationale AWS ELB (Elastic Load Balancing) is the service we use for exposing applications to the Internet. It provides load balancers using an IaaS model. The main reasons why we chose it over other alternatives are the following: It seamlessly ...
EKS
Rationale AWS EKS (Elastic Kubernetes Service) is the service we use for hosting our Kubernetes Cluster in the cloud. It allows us to completely manage the system using an IaaS approach. The main reasons why we chose it over other alternatives are ...
EC2
Rationale AWS EC2 (Elastic Compute Cloud) is the service we use for running computing machines on the cloud. It provides the required infrastructure for services like our CI, Kubernetes Cluster, among others. The main reasons why we chose it over ...
EBS
Rationale AWS EBS (Elastic Block Store) is the service we use for block-level storage. It allows us to have hard drives in the cloud. The main reasons why we chose it over other alternatives are the following: It seamlessly integrates with AWS EC2, ...
DynamoDB
Rationale DynamoDB is the database we use for storing all the business-related data in our platform. The main reasons why we chose it over other alternatives are the following: It is a NoSQL database service whose premise is to be performant and ...
Cost Management
Rationale We use Cost Management for controlling and optimizing our costs within AWS. The main reasons why we chose it over other alternatives are the following: It is a core AWS service. Once we start creating infrastructure, Cost Management begins ...
CloudWatch
Rationale We use CloudWatch for monitoring our entire AWS infrastructure. We can monitor our applications, react to performance changes within them, optimize resource utilization, and get a unified view of operational health. The main reasons why we ...
Batch
Rationale We use Batch for running batch processing jobs in the cloud. The main reasons why we chose it over other alternatives are the following: It is SaaS (software as a service), so we do not need to manage any infrastructure directly. It is ...
AWS
AWS (Amazon Web Services) is our main IaaS cloud provider. The main reasons why we chose it over other alternatives are the following: It provides a highly granular approach to IaaS, offering over one hundred independent services that range from ...
BugSnag
Rationale BugSnag is our primary error monitoring tool. It provides error reporting libraries that automatically detect and report errors in real-time in our applications and capture diagnostic data required to help the engineering team reproduce and ...