Magento Fork Platform Development

We are about to build an enterprise grade transactional/commerce platform forked from Magento Community Edition core. This includes the forked software along with the appropriate architecture of scalable infrastructure that the software runs on. Also, it is to include the mobile architecture (for smart phones and tablets) that reads from the forked Magento back-end via the Ionic Framework. This forked platform is to have the ability to be modularly adapted with any application/service we wish to add to our portfolio. It should be future proof for a minimum of 4 years as to regain the development investment made to build, deploy and maintain it. It is important to keep in mind while much of this work requires extremely advanced knowledge of the Magento platform, as we are developing in a more experimental/reverse engineered space, it requires deep knowledge of many other technologies as well. To control specifications and the security of our efforts much of the scaleable infrastructure that the forked software will run on is being provided by us in the AWS cloud. That infrastructure will be fine tuned by the developer/provider and by C&C, as a team. The project will not be taken over by the developer/provider to do as they please. Professional input for optimal systems and software will of course be a part of the process, as within any competent development team. The project requires the developer/provider which is selected is not constrained by a singular way of thought and has the ability to develop in a creative and open way within the scope of the C&C project guidelines. Application Platform: Magento CE/EE Magento Stack: RHEL/CentOS - Apache 2.4+, PHP7+, Javascript, HTML, XML, CSS, MySQL 5.7+, Redis, Varnish, Apache Solr Transaction/Security: SSL/TLS, Stripe, Paypal, PCI DSS Cloud Infrastructure - AWS System Operator: Deploying, managing, and operating scalable, highly available, and fault tolerant systems on AWS Migrating an existing on-premises application to AWS Implementing and controlling the flow of data to and from AWS Selecting the appropriate AWS service based on compute, data, or security requirements Identifying appropriate use of AWS operational best practices Estimating AWS usage costs and identifying operational cost control mechanisms Mobile Platform: iOS & Android Application Development Ionic Framework + Modules AngularJS Node.JS SASS Cordova/PhoneGap Compiling Ionic Creator App Prototyping API's: AWS - Specifically EC2, VPC, S3, Route53, ELB, RDS, ElastiCache, IAM, SNS - [login to view URL] Gandi Provider - [login to view URL] Ionic/AngularJS - [login to view URL] Stripe - [login to view URL] NextCloud - [login to view URL] Zimbra (PHP+Python) - [login to view URL] - [login to view URL] - [login to view URL] Odoo - [login to view URL] SaltStack/Python Client - [login to view URL] Versioning + Automation + Orchestration: Git/GitHub Composer Jenkins SaltStack Docker Identity/Access: SAML OAuth LDAP Active Directory Core Platform (Magento fork + standardized deployment infrastructure to meet future scale demands) - 1 month User Account Base (multi-API centralized control space) - 1 month Domain Purchasing/Management (via Gandi, as a pilot extension, initiating our wider plans for extendable development) - 1 month Pleas submit your price & time quote, with details of how you are going to execute it.