platformOS

Yes, platformOS hosts all types of applications, but we excel in complex web applications. You can build simple landing pages, through advanced many-to-many eCommerce / Community / Service marketplaces for government and banking, up to advanced SaaS products.

Since platformOS provides automated DevOps out of the box, you do not need as many senior backend developers as in the typical team, because the infrastructure is already configured and accessible via GraphQL.Most importantly, you require absolutely zero expensive DevOps engineers.

Yes, platformOS provides all the necessary tools to build SPA. On platformOS you can use any frontend framework you like, like React, Angular, Vue, etc., and leverage GraphQL to build and run your backend API.

Yes, on platformOS you can build backend API that will be consumed by any client - browser, mobile applications. To allow you to build a great and secure experience for your customers, we support service workers, WebSockets, JWT, OAuth.

Yes, the power of platformOS is its flexibility. We achieved it by allowing you to send Api Calls over HTTP(s) using GraphQL. You have full control of the request’s payload and headers. Most importantly, you can process the response and implement the logic depending on the result - which might be saving something to the database, triggering another Api Call etc.

For the FrontEnd, you can use any technology you like - you own the build process of the assets, so you can use any preprocessors and postprocessors for CSS and JS, any framework like React, Angular, Vue, etc..

For the server side, we have implemented GraphQL queries and mutations that allow you to integrate with every infrastructure component. As a server-side glue code for full flexibility, you can leverage Liquid

Our main goal in platformOS is to reduce cognitive load for developers as much as possible. We have done it by using GraphQL and Liquid as an abstraction layer for the hard parts of backend programming - DevOps, SecOps, Database Management, Session Management, etc.  Developers working on platformOS have to focus on implementing business logic, meaning a successful developer would have strong problem-solving skills. GraphQL and Liquid were designed to be easy to use and learn and are successfully used by big players like Facebook, Shopify, Microsoft, and IBM.

On top of that, we have created tools like pos-cli, platformos-check to make it easy even for junior developers to build advanced applications using platformOS successfully.

The main reason is security - Liquid operates within a sandbox-like environment, ensuring that only explicitly allowed operations are executed. Unlike many programming languages such as Python, PHP, and Java, Liquid is tailored for enhanced security. It's a great fit for us, because it allows us to provide multi-tenant environments, enabling each customer to access code without risking unauthorized data access from other tenants.

Yes, our GUI available via pos-cli is making use of that. By default it would require the developer’s token, however in one minute, one can create a custom endpoint that would invoke GraphQL provided as a parameter, and add any authentication and authorization to it as needed.

At this stage we do not allow accessing the database directly - one needs to use GraphQL to perform DB operations. There are multiple reasons for this, the most important ones are that we can optimize indexes/queries behind the scenes and that each of the environments is multi-tenant by default.

There are many secure defaults, which protect developers from introducing vulnerabilities to the application powered by platformOS. To name a few:

• All variables are by default escaped, preventing various types of XSS Attack
• User built-in model handles industry best practices like hashing the password with a one-way hashing function before persisting it, provides a secure implementation for authentication either by email/password, JWT, including 2FA support etc.
• A new session is created when a user logs in, preventing all kinds of session fixation attacks
• Each POST endpoint requires CSRF Token to prevent a potential Cross-Site Request Forgery attack.
• Due to the usage of GraphQL, an application powered by platformOS is not vulnerable to SQL Injection attacks, because developers do not write SQLs, and we ensure with static analysis tools that implementation of the graphql mutations/query does not make it possible to perform SQL injection.

Yes, we claim that we are provider agnostic, and platformOS Stack can be hosted on any infrastructure provider. Contact us to discuss details.

Yes, contact us to discuss details.