Alternatives to Appwrite logo

Alternatives to Appwrite

Firebase, Parse, Postman, Insomnia REST Client, and OpenAPI are the most popular alternatives and competitors to Appwrite.
67
156
+ 1
54

What is Appwrite and what are its top alternatives?

Appwrite's open-source platform lets you add Auth, DBs, Functions and Storage to your product and build any application at any scale, own your data, and use your preferred coding languages and tools.
Appwrite is a tool in the API Tools category of a tech stack.
Appwrite is an open source tool with 40.5K GitHub stars and 3.6K GitHub forks. Here’s a link to Appwrite's open source repository on GitHub

Top Alternatives to Appwrite

  • Firebase
    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Parse
    Parse

    With Parse, you can add a scalable and powerful backend in minutes and launch a full-featured app in record time without ever worrying about server management. We offer push notifications, social integration, data storage, and the ability to add rich custom logic to your app’s backend with Cloud Code. ...

  • Postman
    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Insomnia REST Client
    Insomnia REST Client

    Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux. ...

  • RestSharp
    RestSharp

    It is probably the most popular HTTP client library for .NET. Featuring automatic serialization and deserialization, request and response type detection, variety of authentications and other useful features ...

  • OpenAPI
    OpenAPI

    It is a publicly available application programming interface that provides developers with programmatic access to a proprietary software application or web service. ...

  • Retrofit
    Retrofit

    Retrofit turns your HTTP API into a Java interface

  • OpenAPI Specification
    OpenAPI Specification

    It defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. ...

Appwrite alternatives & related posts

Firebase logo

Firebase

40.5K
34.3K
2K
The Realtime App Platform
40.5K
34.3K
+ 1
2K
PROS OF FIREBASE
  • 371
    Realtime backend made easy
  • 270
    Fast and responsive
  • 242
    Easy setup
  • 215
    Real-time
  • 191
    JSON
  • 134
    Free
  • 128
    Backed by google
  • 83
    Angular adaptor
  • 68
    Reliable
  • 36
    Great customer support
  • 32
    Great documentation
  • 25
    Real-time synchronization
  • 21
    Mobile friendly
  • 18
    Rapid prototyping
  • 14
    Great security
  • 12
    Automatic scaling
  • 11
    Freakingly awesome
  • 8
    Super fast development
  • 8
    Angularfire is an amazing addition!
  • 8
    Chat
  • 6
    Built in user auth/oauth
  • 6
    Ios adaptor
  • 6
    Awesome next-gen backend
  • 6
    Firebase hosting
  • 4
    Speed of light
  • 4
    Very easy to use
  • 3
    Great
  • 3
    It's made development super fast
  • 3
    Brilliant for startups
  • 2
    The concurrent updates create a great experience
  • 2
    Push notification
  • 2
    .net
  • 2
    Cloud functions
  • 2
    Free hosting
  • 2
    Free authentication solution
  • 2
    JS Offline and Sync suport
  • 2
    Low battery consumption
  • 2
    I can quickly create static web apps with no backend
  • 2
    Great all-round functionality
  • 1
    Large
  • 1
    Easy to use
  • 1
    Free SSL
  • 1
    Faster workflow
  • 1
    Google's support
  • 1
    CDN & cache out of the box
  • 1
    Easy Reactjs integration
  • 1
    Simple and easy
  • 1
    Good Free Limits
  • 1
    Serverless
CONS OF FIREBASE
  • 31
    Can become expensive
  • 16
    No open source, you depend on external company
  • 15
    Scalability is not infinite
  • 9
    Not Flexible Enough
  • 7
    Cant filter queries
  • 3
    Very unstable server
  • 3
    No Relational Data
  • 2
    Too many errors
  • 2
    No offline sync

related Firebase posts

Stephen Gheysens
Lead Solutions Engineer at Inscribe · | 14 upvotes · 1.8M views

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

See more
Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Parse logo

Parse

522
479
600
The complete mobile app platform
522
479
+ 1
600
PROS OF PARSE
  • 118
    Easy setup
  • 78
    Free hosting
  • 62
    Well-documented
  • 52
    Cheap
  • 47
    Use push notifications in 3 lines of code
  • 41
    Fast
  • 39
    Cloud code
  • 32
    Good for prototypes
  • 31
    Cloud modules
  • 27
    Backed by facebook
  • 7
    Cross Platform
  • 7
    Parse Push
  • 6
    Parse Analytics
  • 6
    Multiplatform
  • 6
    Parse Core
  • 5
    Quick chat and profile capabilities
  • 5
    Free Tier
  • 5
    Cloud Based
  • 4
    Free
  • 4
    Nice security concept
  • 3
    Backbone Models
  • 3
    Local Datastore
  • 3
    Backend as a service
  • 3
    Geopoints
  • 2
    Easy to use
  • 2
    Anonymous Users
  • 2
    About to Die
CONS OF PARSE
    Be the first to leave a con

    related Parse posts

    Postman logo

    Postman

    92.2K
    78.8K
    1.8K
    Only complete API development environment
    92.2K
    78.8K
    + 1
    1.8K
    PROS OF POSTMAN
    • 490
      Easy to use
    • 369
      Great tool
    • 276
      Makes developing rest api's easy peasy
    • 156
      Easy setup, looks good
    • 144
      The best api workflow out there
    • 53
      It's the best
    • 53
      History feature
    • 44
      Adds real value to my workflow
    • 43
      Great interface that magically predicts your needs
    • 35
      The best in class app
    • 12
      Can save and share script
    • 10
      Fully featured without looking cluttered
    • 8
      Collections
    • 8
      Option to run scrips
    • 8
      Global/Environment Variables
    • 7
      Shareable Collections
    • 7
      Dead simple and useful. Excellent
    • 7
      Dark theme easy on the eyes
    • 6
      Awesome customer support
    • 6
      Great integration with newman
    • 5
      Documentation
    • 5
      Simple
    • 5
      The test script is useful
    • 4
      Saves responses
    • 4
      This has simplified my testing significantly
    • 4
      Makes testing API's as easy as 1,2,3
    • 4
      Easy as pie
    • 3
      API-network
    • 3
      I'd recommend it to everyone who works with apis
    • 3
      Mocking API calls with predefined response
    • 2
      Now supports GraphQL
    • 2
      Postman Runner CI Integration
    • 2
      Easy to setup, test and provides test storage
    • 2
      Continuous integration using newman
    • 2
      Pre-request Script and Test attributes are invaluable
    • 2
      Runner
    • 2
      Graph
    • 1
      <a href="http://fixbit.com/">useful tool</a>
    CONS OF POSTMAN
    • 10
      Stores credentials in HTTP
    • 9
      Bloated features and UI
    • 8
      Cumbersome to switch authentication tokens
    • 7
      Poor GraphQL support
    • 5
      Expensive
    • 3
      Not free after 5 users
    • 3
      Can't prompt for per-request variables
    • 1
      Import swagger
    • 1
      Support websocket
    • 1
      Import curl

    related Postman posts

    Noah Zoschke
    Engineering Manager at Segment · | 30 upvotes · 2.7M views

    We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

    Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

    Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

    This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

    Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

    Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

    Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

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

    Our whole Node.js backend stack consists of the following tools:

    • Lerna as a tool for multi package and multi repository management
    • npm as package manager
    • NestJS as Node.js framework
    • TypeScript as programming language
    • ExpressJS as web server
    • Swagger UI for visualizing and interacting with the API’s resources
    • Postman as a tool for API development
    • TypeORM as object relational mapping layer
    • JSON Web Token for access token management

    The main reason we have chosen Node.js over PHP is related to the following artifacts:

    • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
    • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
    • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
    • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
    See more
    Insomnia REST Client logo

    Insomnia REST Client

    779
    640
    44
    The most intuitive cross-platform REST API Client 😴
    779
    640
    + 1
    44
    PROS OF INSOMNIA REST CLIENT
    • 16
      Easy to work with
    • 11
      Great user interface
    • 6
      Works with GraphQL
    • 4
      Cross platform, available for Mac, Windows, and Linux
    • 3
      Opensource
    • 2
      Vim and Emacs key map
    • 2
      Preserves request templates
    • 0
      Does not have history feature
    CONS OF INSOMNIA REST CLIENT
    • 4
      Do not have team sharing options
    • 2
      Do not store credentials in HTTP

    related Insomnia REST Client posts

    Jason Barry
    Cofounder at FeaturePeek · | 4 upvotes · 2.4M views

    We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

    • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
    • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
    • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

    Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

    See more
    RestSharp logo

    RestSharp

    767
    36
    0
    Simple REST and HTTP API Client for .NET
    767
    36
    + 1
    0
    PROS OF RESTSHARP
      Be the first to leave a pro
      CONS OF RESTSHARP
        Be the first to leave a con

        related RestSharp posts

        OpenAPI logo

        OpenAPI

        614
        431
        6
        Allows the owner of a network-accessible service to give universal access
        614
        431
        + 1
        6
        PROS OF OPENAPI
        • 1
          Easy to read the template generated
        • 1
          The most popular api spec
        • 1
          Easy to learn
        • 1
          Supports versioning
        • 1
          Supports authentication
        • 1
          Supports caching
        CONS OF OPENAPI
          Be the first to leave a con

          related OpenAPI posts

          Joshua Dean Küpper
          CEO at Scrayos UG (haftungsbeschränkt) · | 4 upvotes · 469.6K views

          We use Swagger Inspector in conjunction with our universal REST-API "Charon". Swagger Inspector makes testing edge-cases hassle-free and lets testing look easy. Swagger Inspector was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.

          We previously used Postman but decided to switch over to Swagger Inspector because it also integrated seamlessly into Swagger UI, which we use for displaying our OpenAPI specification of said REST-API.

          See more
          Retrofit logo

          Retrofit

          377
          197
          0
          A type-safe HTTP client for Android and Java
          377
          197
          + 1
          0
          PROS OF RETROFIT
            Be the first to leave a pro
            CONS OF RETROFIT
              Be the first to leave a con

              related Retrofit posts

              OpenAPI Specification logo

              OpenAPI Specification

              257
              145
              10
              An API description format for REST APIs
              257
              145
              + 1
              10
              PROS OF OPENAPI SPECIFICATION
              • 5
                API Documentation
              • 5
                API Specification
              CONS OF OPENAPI SPECIFICATION
                Be the first to leave a con

                related OpenAPI Specification posts