Alternatives to PythonAnywhere logo

Alternatives to PythonAnywhere

Heroku, Google App Engine, Codeanywhere, DigitalOcean, and Linode are the most popular alternatives and competitors to PythonAnywhere.
88
270
+ 1
63

What is PythonAnywhere and what are its top alternatives?

It's somewhat unique. A small PaaS that supports web apps (Python only) as well as scheduled jobs with shell access. It is an expensive way to tinker and run several small apps.
PythonAnywhere is a tool in the Platform as a Service category of a tech stack.

Top Alternatives to PythonAnywhere

  • Heroku
    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • Google App Engine
    Google App Engine

    Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. ...

  • Codeanywhere
    Codeanywhere

    A development platform that enables you to not only edit your files from underlying services like FTP, GitHub, Dropbox and the like, but on top of that gives you the ability to collaborate, embed and share through Codeanywhere on any device. ...

  • DigitalOcean
    DigitalOcean

    We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel. ...

  • Linode
    Linode

    Get a server running in minutes with your choice of Linux distro, resources, and node location. ...

  • WebFaction
    WebFaction

    No need to spend hours installing and configuring the software, database and other tools. We have over 50 one-click installers in our control panel. ...

  • Apollo
    Apollo

    Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes. ...

  • AWS Elastic Beanstalk
    AWS Elastic Beanstalk

    Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring. ...

PythonAnywhere alternatives & related posts

Heroku logo

Heroku

22.2K
17.7K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
22.2K
17.7K
+ 1
3.2K
PROS OF HEROKU
  • 704
    Easy deployment
  • 459
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
  • 190
    Easy setup
  • 174
    Add-ons for almost everything
  • 153
    Beginner friendly
  • 150
    Better for startups
  • 133
    Low learning curve
  • 48
    Postgres hosting
  • 41
    Easy to add collaborators
  • 30
    Faster development
  • 24
    Awesome documentation
  • 19
    Simple rollback
  • 19
    Focus on product, not deployment
  • 15
    Natural companion for rails development
  • 15
    Easy integration
  • 12
    Great customer support
  • 8
    GitHub integration
  • 6
    Painless & well documented
  • 6
    No-ops
  • 4
    I love that they make it free to launch a side project
  • 4
    Free
  • 3
    Great UI
  • 3
    Just works
  • 2
    PostgreSQL forking and following
  • 2
    MySQL extension
  • 1
    Security
  • 1
    Able to host stuff good like Discord Bot
  • 0
    Sec
CONS OF HEROKU
  • 24
    Super expensive
  • 7
    Not a whole lot of flexibility
  • 5
    No usable MySQL option
  • 5
    Storage
  • 4
    Low performance on free tier
  • 1
    24/7 support is $1,000 per month

related Heroku posts

Russel Werner
Lead Engineer at StackShare · | 32 upvotes · 1.6M views

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.4M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Google App Engine logo

Google App Engine

8.3K
6.5K
609
Build web applications on the same scalable systems that power Google applications
8.3K
6.5K
+ 1
609
PROS OF GOOGLE APP ENGINE
  • 144
    Easy to deploy
  • 106
    Auto scaling
  • 80
    Good free plan
  • 62
    Easy management
  • 56
    Scalability
  • 35
    Low cost
  • 32
    Comprehensive set of features
  • 28
    All services in one place
  • 22
    Simple scaling
  • 19
    Quick and reliable cloud servers
  • 6
    Granular Billing
  • 5
    Easy to develop and unit test
  • 4
    Monitoring gives comprehensive set of key indicators
  • 3
    Create APIs quickly with cloud endpoints
  • 3
    Really easy to quickly bring up a full stack
  • 2
    No Ops
  • 2
    Mostly up
CONS OF GOOGLE APP ENGINE
    Be the first to leave a con

    related Google App Engine posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 11 upvotes · 320.6K views

    So, the shift from Amazon EC2 to Google App Engine and generally #AWS to #GCP was a long decision and in the end, it's one that we've taken with eyes open and that we reserve the right to modify at any time. And to be clear, we continue to do a lot of stuff with AWS. But, by default, the content of the decision was, for our consumer-facing products, we're going to use GCP first. And if there's some reason why we don't think that's going to work out great, then we'll happily use AWS. In practice, that hasn't really happened. We've been able to meet almost 100% of our needs in GCP.

    So it's basically mostly Google Kubernetes Engine , we're mostly running stuff on Kubernetes right now.

    #AWStoGCPmigration #cloudmigration #migration

    See more
    Aliadoc Team

    In #Aliadoc, we're exploring the crowdfunding option to get traction before launch. We are building a SaaS platform for website design customization.

    For the Admin UI and website editor we use React and we're currently transitioning from a Create React App setup to a custom one because our needs have become more specific. We use CloudFlare as much as possible, it's a great service.

    For routing dynamic resources and proxy tasks to feed websites to the editor we leverage CloudFlare Workers for improved responsiveness. We use Firebase for our hosting needs and user authentication while also using several Cloud Functions for Firebase to interact with other services along with Google App Engine and Google Cloud Storage, but also the Real Time Database is on the radar for collaborative website editing.

    We generally hate configuration but honestly because of the stage of our project we lack resources for doing heavy sysops work. So we are basically just relying on Serverless technologies as much as we can to do all server side processing.

    Visual Studio Code definitively makes programming a much easier and enjoyable task, we just love it. We combine it with Bitbucket for our source code control needs.

    See more
    Codeanywhere logo

    Codeanywhere

    98
    227
    120
    Online code editor, available on iOS, Android and more. Integrates with GitHub and Dropbox
    98
    227
    + 1
    120
    PROS OF CODEANYWHERE
    • 16
      Sleek interface
    • 16
      3rd party integration
    • 13
      Easy to use
    • 11
      Web IDE
    • 9
      Fast loading
    • 9
      FTP support
    • 7
      Emmet
    • 5
      Full root access
    • 5
      Anywhere coding
    • 5
      SSH Connections for free
    • 4
      SFTP support
    • 4
      Private use for free
    • 4
      Preconfigured development stacks
    • 4
      GitHub integration
    • 3
      Easy setup
    • 2
      Easy Setup, Containers
    • 2
      Amazon S3 Integration
    • 1
      Code directly by FTP
    CONS OF CODEANYWHERE
      Be the first to leave a con

      related Codeanywhere posts

      DigitalOcean logo

      DigitalOcean

      15.5K
      11.2K
      2.6K
      Deploy an SSD cloud server in less than 55 seconds with a dedicated IP and root access.
      15.5K
      11.2K
      + 1
      2.6K
      PROS OF DIGITALOCEAN
      • 559
        Great value for money
      • 364
        Simple dashboard
      • 362
        Good pricing
      • 300
        Ssds
      • 250
        Nice ui
      • 192
        Easy configuration
      • 155
        Great documentation
      • 138
        Ssh access
      • 135
        Great community
      • 24
        Ubuntu
      • 13
        Docker
      • 12
        IPv6 support
      • 10
        Private networking
      • 8
        99.99% uptime SLA
      • 7
        Simple API
      • 7
        Great tutorials
      • 6
        55 Second Provisioning
      • 5
        One Click Applications
      • 4
        Dokku
      • 4
        Node.js
      • 4
        Debian
      • 4
        CoreOS
      • 4
        LAMP
      • 3
        LEMP
      • 3
        Ghost
      • 3
        Simple Control Panel
      • 3
        Word Press
      • 3
        1Gb/sec Servers
      • 2
        Quick and no nonsense service
      • 2
        Speed
      • 2
        Mean
      • 2
        Hex Core machines with dedicated ECC Ram and RAID SSD s
      • 2
        Django
      • 2
        Runs CoreOS
      • 2
        Good Tutorials
      • 2
        GitLab
      • 2
        Ruby on Rails
      • 1
        CentOS
      • 1
        Spaces
      • 1
        KVM Virtualization
      • 1
        Amazing Hardware
      • 1
        Transfer Globally
      • 1
        Fedora
      • 1
        FreeBSD
      • 1
        Drupal
      • 1
        FreeBSD Amp
      • 1
        Magento
      • 1
        ownCloud
      • 1
        RedMine
      • 1
        My go to server provider
      • 1
        Ease and simplicity
      • 1
        Nice
      • 1
        Find it superfitting with my requirements (SSD, ssh.
      • 1
        Easy Setup
      • 1
        Cheap
      • 1
        Static IP
      • 1
        It's the easiest to get started for small projects
      • 1
        Automatic Backup
      • 1
        Great support
      • 1
        Quick and easy to set up
      • 1
        Servers on demand - literally
      • 1
        Reliability
      • 0
        Variety of services
      • 0
        Managed Kubernetes
      CONS OF DIGITALOCEAN
      • 3
        Pricing
      • 3
        No live support chat

      related DigitalOcean posts

      Hello, I'm currently writing an e-commerce website with Laravel and Laravel Nova (as an admin panel). I want to start deploying the app and created a DigitalOcean account. After some searches about the deployment process, I saw that the setup via DigitalOcean (using Droplets) isn't very easy for beginners. Now I'm not sure how to deploy my app. I am in between Laravel Forge and DigitalOcean (?Apps Platform or Droplets?). I've read that Heroku and Laravel Vapor are a bit expensive. That's why I didn't consider them yet. I'd be happy to read your opinions on that topic!

      See more

      Hi, I'm a beginner at using MySQL, I currently deployed my crud app on Heroku using the ClearDB add-on. I didn't see that coming, but the increased value of the primary key instead of being 1 is set to 10, and I cannot find a way to change it. Now I`m considering switching and deploying the full app and MySql to DigitalOcean any advice on that? Will I get the same issue? Thanks in advance!

      See more
      Linode logo

      Linode

      711
      588
      420
      Deploy and Manage Linux Virtual Servers in the Linode Cloud.
      711
      588
      + 1
      420
      PROS OF LINODE
      • 100
        Extremely reliable
      • 70
        Good value
      • 59
        Great customer support
      • 58
        Easy to configure
      • 36
        Great documentation
      • 24
        Servers across the world
      • 18
        Managed/hosted DNS service
      • 15
        Simple ui
      • 11
        Network and CPU usage graphs
      • 7
        IPv6 support
      • 6
        Multiple IP address support
      • 3
        Ssh access
      • 3
        Good price, good cusomter sevice
      • 2
        IP address fail over support
      • 2
        SSH root access
      • 1
        Great performance compared to EC2 or DO
      • 1
        It runs apps with speed
      • 1
        Best customizable VPS
      • 1
        Latest kernels
      • 1
        Cheapest
      • 1
        Ssds
      CONS OF LINODE
      • 2
        No "floating IP" support

      related Linode posts

      Kumar Gaurav
      DevOps Engineer at CoRover Private Limited · | 2 upvotes · 24.8K views
      Shared insights
      on
      Microsoft AzureMicrosoft AzureLinodeLinode

      What is the data transfer out cost (Bandwidth cost) on Linode compared to Microsoft Azure?

      See more
      WebFaction logo

      WebFaction

      31
      48
      18
      Hosting for developers: full shell access to fast servers with all your favorite tools pre-installed and maintained for...
      31
      48
      + 1
      18
      PROS OF WEBFACTION
      • 3
        Cost effective
      • 3
        Great customer support
      • 3
        Servers administered for you
      • 2
        Comes with Rails installed automatically
      • 1
        Great documentation
      • 1
        SSH access
      • 1
        Best price
      • 1
        SSD
      • 1
        Many pre-installed apps
      • 1
        Having the least amount of new "fancy" terminologies
      • 1
        No needs configuration
      CONS OF WEBFACTION
        Be the first to leave a con

        related WebFaction posts

        Apollo logo

        Apollo

        2.1K
        1.6K
        19
        GraphQL server for Express, Connect, Hapi, Koa and more
        2.1K
        1.6K
        + 1
        19
        PROS OF APOLLO
        • 12
          From the creators of Meteor
        • 3
          Great documentation
        • 2
          Open source
        • 2
          Real time if use subscription
        CONS OF APOLLO
        • 1
          File upload is not supported
        • 1
          Increase in complexity of implementing (subscription)

        related Apollo posts

        Nick Rockwell
        SVP, Engineering at Fastly · | 44 upvotes · 2M views

        When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

        So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

        React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

        Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

        See more
        Adam Neary

        At Airbnb we use GraphQL Unions for a "Backend-Driven UI." We have built a system where a very dynamic page is constructed based on a query that will return an array of some set of possible “sections.” These sections are responsive and define the UI completely.

        The central file that manages this would be a generated file. Since the list of possible sections is quite large (~50 sections today for Search), it also presumes we have a sane mechanism for lazy-loading components with server rendering, which is a topic for another post. Suffice it to say, we do not need to package all possible sections in a massive bundle to account for everything up front.

        Each section component defines its own query fragment, colocated with the section’s component code. This is the general idea of Backend-Driven UI at Airbnb. It’s used in a number of places, including Search, Trip Planner, Host tools, and various landing pages. We use this as our starting point, and then in the demo show how to (1) make and update to an existing section, and (2) add a new section.

        While building your product, you want to be able to explore your schema, discovering field names and testing out potential queries on live development data. We achieve that today with GraphQL Playground, the work of our friends at #Prisma. The tools come standard with Apollo Server.

        #BackendDrivenUI

        See more
        AWS Elastic Beanstalk logo

        AWS Elastic Beanstalk

        2.1K
        1.7K
        240
        Quickly deploy and manage applications in the AWS cloud.
        2.1K
        1.7K
        + 1
        240
        PROS OF AWS ELASTIC BEANSTALK
        • 77
          Integrates with other aws services
        • 65
          Simple deployment
        • 44
          Fast
        • 28
          Painless
        • 16
          Free
        • 3
          Independend app container
        • 3
          Well-documented
        • 2
          Postgres hosting
        • 2
          Ability to be customized
        CONS OF AWS ELASTIC BEANSTALK
        • 2
          Charges appear automatically after exceeding free quota
        • 1
          Lots of moving parts and config
        • 0
          Slow deployments

        related AWS Elastic Beanstalk posts

        Julien DeFrance
        Principal Software Engineer at Tophatter · | 16 upvotes · 2.5M views

        Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

        I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

        For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

        Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

        Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

        Future improvements / technology decisions included:

        Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

        As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

        One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

        See more

        We initially started out with Heroku as our PaaS provider due to a desire to use it by our original developer for our Ruby on Rails application/website at the time. We were finding response times slow, it was painfully slow, sometimes taking 10 seconds to start loading the main page. Moving up to the next "compute" level was going to be very expensive.

        We moved our site over to AWS Elastic Beanstalk , not only did response times on the site practically become instant, our cloud bill for the application was cut in half.

        In database world we are currently using Amazon RDS for PostgreSQL also, we have both MariaDB and Microsoft SQL Server both hosted on Amazon RDS. The plan is to migrate to AWS Aurora Serverless for all 3 of those database systems.

        Additional services we use for our public applications: AWS Lambda, Python, Redis, Memcached, AWS Elastic Load Balancing (ELB), Amazon Elasticsearch Service, Amazon ElastiCache

        See more