Blog

Heroku's varied and often platform-specific ways of deploying your application can make it difficult to understand the best way to migrate to another Platform as a Service. We're offering this guide to help you understand the flexible options you have for migrating an application from Heroku to Aptible.

In today’s security conscious B2C and B2B markets, companies, especially those operating in high compliance industries like healthcare, have to be mindful of planning, implementing and maintaining good-practice security. This can quickly prove daunting for teams unfamiliar with the intricacies of interpreting regulations and frameworks like HIPAA, HITRUST and SOC 2 into meaningful implementation, maintenance and monitoring details in their software development lifecycle and infrastructure. Add to this the ever-changing security expectations of customers and auditors on what it means to be secure and compliant, and software engineers spend more time maintaining and proving their security posture and less time building value for their target market. 

Today, we’re excited to introduce Conveyor, a customer trust platform born out of the insights obtained building Aptible Comply. Conveyor is a new company spun out of Aptible whose mission is to build a more trustworthy internet by creating a network of customers and vendors that makes it simple to build trust through data security.

Announcing Log Drain Improvements for High-Performant, Reliable Delivery to External Destinations.

Aptible’s UX Engineering team has recently launched version 1.0 of our in-house design system, Arrow Design System (Arrow DS for short). In this post, I’m going to walk you through some of the frameworks and tools we use and show off one of our more complicated components.

createSlice is a higher-order function that accepts the slice name (e.g. token, user, todos), a set of reducers, and returns a single reducer along with the action creators for that reducer. The goal of createSlice is to reduce the boilerplate required to add data to redux the canonical way.

If you have a product and customers, then you also have members of your team who need access to critical systems in order for your company to function. Safeguarding credentials that can access these systems via mechanisms like 2FA, U2F, and key rotation is necessary but not sufficient. You must also monitor for key security events and review each to ensure your protections are working as intended.

We recently rolled out updated HTTP security headers for Comply. Following best practices with HTTP security headers can be a quick way to add an additional layer of security to a website, so we wanted to share our work here in hopes that others might find it helpful.

The landscape of front-end engineering has changed drastically in the last few years. In the past, front-end engineers were depended upon to translate design comps into functioning HTML, CSS and JavaScript. More recently, with the explosion of the JavaScript ecosystem, front-end engineers are now expected to work more broadly across the entire stack, and in some cases, have more of a traditional computer science background. So is there still a place for front-end engineers who still enjoy writing CSS?