Maintaining our reputation as an innovative leader in the world of finance requires an incredibly reliable and secure system for processing financial transactions. Our engineers get us there. Read about how we get it done.
SWE-Lancer is a benchmark developed by OpenAI that evaluates LLMs using actual freelance software tasks from Expensify’s open-source repository. Let’s explore how Expensify contributed to the SWE-Lancer project and what this means for the future of AI in software engineering.
Here’s a deep dive into how Expensify's core hardware works – down to the chip level – with an explanation of how that enables a critical feature of our software to work. We hope you'll find it useful as you architect your own NUMA-balanced applications on your own high-density servers!
I wanted to quickly take a moment to apologize for some performance and reliability issues we had a couple weeks back. In the spirit of transparency, here are comprehensive details on what happened, how it was fixed, and how we will ensure better reliability going forward.
If you were trying to get shit done on your expense reports around 3:30am UTC on June 16th, you would’ve noticed we had a site outage. Here are the details of our Incident Response to enhance our own learnings and behaviors for next time, and spread that knowledge with our community.
Expensify has an unusual technology stack in many ways. But most surprising of all is that we don't use MySQL or Postgres — instead using none other than SQLite — and it works great.
This month marks the sixth anniversary of Expensify. In May 2008, David Barrett got the idea of a world where expenses reports don't have to suck. Learn more in this blog post.
Last month we announced Amex Corporate Card Reconciliation and received a huge enthusiastic response from our users. Due to the popularity of the feature and user demand, we have expanded Corporate Card Reconciliation to many more major banks.
