Custom Co-Browser Backend Service
Budget: $5,000 – $15,000 USD
The project is to create a virtual co-browsing application, allowing multiple users to interact with a remote browser, embedded in a browser. Users need to be able to request a remote browser on demand. The remote browser will only exist for the duration of the user session. After that the remote browser session needs to be persisted and the instance stopped.
Don't worry about the front-end application / user interface - I already have a browser-based frontend app that this will plug into.
This project consists of 3 parts:
1. Client side remote browser (client) - Running in a client browser
2. Server side browser (backend) - Running in a container / virtual machine
3. Infrastructure to request a browser (infrastructure) - Running backend instances in a data center
Please research and, in your bid, provide suggestions on what you think would be the best fit infrastructure- wise to comply with the below listed requirements... this will help me weed out the bots.
Requirements:
1. The desired remote browser software is Chrome.
2. When a user requests a new remote browser instance, this request should be ideally satisfied within 2-3 seconds. Checkout switchboard.app - they have it down to ~1 second.
3. Low latency communication for fluid streaming
4. Backend instances are disposable, can be shutdown at any time to stop incurring costs
5. But browser sessions must be persisted (cookies etc.)
6. Requesting a browser instance with the same ID needs to restore the previously saved session
7. Affordable infrastructure pricing
8. Browsers need to be isolated from each other, to guarantee no other clients can access sensitive data (security)
9. Connection to a remote browser must be only available with a password
10. Multi-user support, displaying named cursors for each remote user joined into the session
Payment will be made in thirds, upon proof of completion of each of the 3 parts in the order listed above. You will be required to sign an NDA and IP Ownership agreement.
Don't worry about the front-end application / user interface - I already have a browser-based frontend app that this will plug into.
This project consists of 3 parts:
1. Client side remote browser (client) - Running in a client browser
2. Server side browser (backend) - Running in a container / virtual machine
3. Infrastructure to request a browser (infrastructure) - Running backend instances in a data center
Please research and, in your bid, provide suggestions on what you think would be the best fit infrastructure- wise to comply with the below listed requirements... this will help me weed out the bots.
Requirements:
1. The desired remote browser software is Chrome.
2. When a user requests a new remote browser instance, this request should be ideally satisfied within 2-3 seconds. Checkout switchboard.app - they have it down to ~1 second.
3. Low latency communication for fluid streaming
4. Backend instances are disposable, can be shutdown at any time to stop incurring costs
5. But browser sessions must be persisted (cookies etc.)
6. Requesting a browser instance with the same ID needs to restore the previously saved session
7. Affordable infrastructure pricing
8. Browsers need to be isolated from each other, to guarantee no other clients can access sensitive data (security)
9. Connection to a remote browser must be only available with a password
10. Multi-user support, displaying named cursors for each remote user joined into the session
Payment will be made in thirds, upon proof of completion of each of the 3 parts in the order listed above. You will be required to sign an NDA and IP Ownership agreement.