About Pal-E

Open-source tools, production-grade infrastructure, one person behind it all.

Why you can trust the tools

You are handing Pal-E OAuth tokens to your Notion, Gmail, Calendar, and LinkedIn accounts. That is a big ask. Here is why it is a safe one.

The code is open source. Every MCP server and the infrastructure running them are publicly available for you to inspect:

If you want to verify what happens with your data, you can read the source. No black boxes.

Built on production infrastructure experience. Pal-E is not a weekend prototype. It is built by someone with 4+ years of production infrastructure work across AWS, Kubernetes, Terraform, and CI/CD pipelines. At Oddball, working on a federal government application, this meant achieving DORA Elite deployment metrics — the highest tier for software delivery performance. The same engineering discipline applies here.

Professional MCP expertise. The MCP integrations in Pal-E are not hobby projects. At Pure Earth Labs, I built MCP servers for Inflow and Monday.com using a repeatable API to SDK to MCP pattern with Zod for runtime validation. That same architecture powers every Pal-E integration.

Who is behind it

My name is Lucas Draney. I am a Senior DevOps and SRE engineer based in Lehi, Utah. I build and operate Pal-E as a solo project — no VC funding, no team, no corporate structure between you and the person running your infrastructure.

My background spans federal contracting at Oddball (Veterans Affairs systems) and manufacturing and e-commerce infrastructure at Pure Earth Labs. I also hold a psychology degree from Utah Valley University, which shapes how I think about user experience and trust.

When you book an onboarding call or message the bot with a question, you are talking to me directly. There is no support team to route around — you get the person who built it.

References

Professional references available via LinkedIn:

Links