Ship apps to AWS and GCP with a single command.

Ship your first app in seconds

Deploy a static site, api or serverless app to your own AWS or GCP account.

pt signup

Create an account and set up your first workspace

  • create an account

  • invite team members

  • setup your AWS or GCP environments

  • configure your domain to use PowerTools

pt signup 👋 create your first workspace pt new 🎉 create a new service pt dev 🏖 preview code changes locally pt build 📦 build and package code for deployment pt deploy ✈️ deploy a service

Building in the cloud is really hard.

I've been building developer platforms for over 6 years now, time and time again I've noticed the most senior engineers at each company are working to enable "developer productivity".

At PowerTools, we're on a mission to build a platform that will work for startups at day 1 when they need to move fast, but also at 1000+ engineers, when they need to build and support highly customized infrastructure for their team.

Jon
Founder + CEO

Any Stack - Production Ready

Components for your applications

Mix and match to create applications with static, container and serverless components. develop, deploy and operate complex apps that consist of multiple components.

Learn more ->

Static Sites

Ship public and internal JAMstack apps without becoming a CDN expert. Best practices included.

  • instant global deploys

  • automatic dns and ssl

  • automatic CDN integration

  • custom build hooks

  • internal and public applications

  • templates for Next.js, Hugo, React and more

---
environments:
- prod
components:
- type: public-static
cmd: /app/scripts/build
# dev configurations
dev_cmd: /app/scripts/dev
dev_port: 3000
dev_mounts:
- src => /app/src
hook: /app/scripts/lint
route: static-site.powertools.dev

Build your way

Microservices, monoliths and anything in between.

Combine multiple components in a single app to build a monolith or build microservices by limiting each app to 1 component. Whether your team builds a monolith, microservices or falls somewhere in between - PowerTools will work for you.

Start shipping ->
---
components:
- type: worker
cmd: ./scripts/run
instances: 1-5
hooks:
- ./scripts/lint

Microservices

Decouple frontend, backend and worker + job code into unique services, to support a microservice architecture.

  • instant deploys

  • instant rollbacks

  • deploy components independently

Fully automated

Managed Infrastructure

PowerTools manages your infrastructure for you. When you run pt workspace sync, we automatically spin up cloud resources for your workspace. From kubernetes clusters, to security groups, certificates and network infrastructure - we do it for you, so your team can focus on shipping software, not managing infrastructure.

Create Your First Workspace ->

Workspaces

Workspaces let you pick and choose environments such as stage, test and prod for your team. Deploy as many apps as you would like per environment

  • customizable - add new environments in new regions with a single line of config

  • unlimited environments

  • unlimited apps

---
# workspace.yml
name: my-workspace
environments:
- name: prod
cloud: aws
cloud_region: us-west-1
cloud_account_id: powertools-dev
zones: 2
release_target: true
enable_serverless: false
enable_containers: true
primary: true

Grow with PowerTools

Extend as You Scale

What works on day one, with just a few engineers does not always work at day 1000 with 500 engineers. PowerTools is designed to interoperate with your infrastructure so your application developers and SRE team can extend capabilities as your team scales.

Learn more ->

Connected Environments

Run PowerTools alongside your existing infrastructure by connecting environments to your current AWS and GCP resources

  • let your PowerTools environments co-exist with your existing cloud infra

  • isolate your PowerTools workspace environments in their own accounts or regions

  • set up secure, internal connectivity between PowerTools environments and your infrastructure

---
# connect your prod environment to
# another aws account VPC
connections:
- environment: prod
cloud: aws
cloud_account_id: my-aws-account
cloud_region: us-east-1
vpc_id: my-aws-vpc