|How does i-Neighbour guarantee uptime?
i-Neighbour runs on the Amazon EC2 which offers a highly reliable environment where replacement instances can be rapidly and predictably commissioned. The Amazon EC2 Service Level Agreement commitment is 99.95% availability for each Amazon EC2 Region. Data is backed up regularly and has Multi-AZ deployments which protects your latest database updates against unplanned outages. All our infrastructure is monitored live, continuously (24/7/365) by Amazon CloudWatch to identify and prevent potential problems from occurring.
|How will i-Neighbour keep my data secure?
i-Neighbour uses block level storage volumes by Amazon Elastic Block Store (Amazon EBS). Amazon EBS volumes are essentially hard disks that can be attached to a running Amazon EC2 instance and is especially suited for applications that require a database, a file system, or access to raw block level storage. EBS volumes store data redundantly, making them more durable than a typical hard drive. The annual failure rate (AFR) for an EBS volume is 0.1% and 0.5%, compared to 4% for a commodity hard drive.
|Is there a data back up plan for i-Neighbour?
Yes. We ensure to keep your data safe, reliable and accessible to you at all times. We prepare for every potential disaster. All data is protected through regularly scheduled full and incremental backups and backup data is shipped to a secured offsite backup location on a regular (scheduled) basis to secure it further. We do both data and server snapshot from time to time. Even if there are some server or hardware failure, it will be able to get back online in a very short period.
|What operational practices does i-Neighbour adheres to, to ensure upgrades are done without disruption?
Most companies who have gone through software upgrade would rather live without it. We relive that headache for you by ensuring we provide seamless upgrades without disruption to your business. All upgrades will be done on the i-Neighbour infrastructure and application level without any user interference. Since we developed the i-Neighbour and have complete control of it, our upgrade is very minimal and only applies to the specific files rather than doing the whole installation and uninstallation.
|How i-Neighbour manage upgrade release and system change?
Changes to our systems and products are thoroughly tested in a variety of pre-production labs by different teams, including Development, Quality Assurance, and Operations. These tests ensures that only high-quality, well-developed changes make it into the "live" environment, and minimizes the impact and downtime you experience.
|What are the integration capabilities?
Currently, all the data from i-Neighbour is provided as it is. No further direct integration or API calls is available for third party application. Anyway, you could still use our data export feature to get your desired output for payroll processing.
|Is i-Neighbour application scalable?
Yes. As your business grows, you can easily add your new terminal or user to i-Neighbour without any disruption from our service. With Amazon EC2, it enables us to increase or decrease capacity within minutes, not hours or days. We can commission one, hundreds or even thousands of server instances simultaneously to cater to our needs.
|Is i-Neighbour Multi-tenant SaaS or ASP?
With i-Neighbour, we are working on integrating and adding another centralized user data layer to realise the Multi-tenant SaaS. As such, multiple customers are sharing the same piece of application and database. The number of databases grows when one exceeded its limit and these greatly reduce the amount of maintenance and troubleshooting work.
|Comparison between Multi-tenant and ASP
|One instance of the software across all customers ensures maintenance and upgrades are painless.
|Each customer's solution is run on a separate instance, making the software difficult to maintain and upgrade. This causes more disruption to your service.
|Customizations are easy, as the software usually includes a configurable interface. This means less time and cost for you to implement and start seeing value.
|Customizations are time-consuming and costly, with little or no easy-to-use configuration options. Implementation is painful, and it takes some time before you start to see value.
|Configurations and customizations are upgraded seamlessly.
|Each instance is upgraded individually. Errors are common, and it's likely that many customizations have to be redone.
|Costs are lower for the vendor to operate, which translates to lower prices for customers.
|Costs are higher for the vendor, resulting in higher pricing as more customers are added.
|It's easy to adhere to the Service Level Agreement, monitoring your service and fixing problems long before they impact your business.
|It's nearly impossible to adhere to the Service Level Agreement, as it's a nightmare to monitor individual instances. Disruptions in service are highly likely.
|Support is available for tens of thousands of users, making it easy for the vendor to become a market-leader.
|Support is good when the customer base is small - typically in the hundreds, forcing the vendor to limit the number of customers if they want to continue providing quality service.