The invoice is a mystery
Four services, three of them unused, on a currency that moves with the exchange rate. Nobody can say which line keeps the site online.
Services
The bill arrives every month and nobody can explain the line items. The site is slow on Thursday afternoons, the connection drops in a storm, and whoever set up the server left a folder of screenshots as documentation. Hosting is a set of decisions about where the data lives and who is called when it stops, not a product you buy once.
Four services, three of them unused, on a currency that moves with the exchange rate. Nobody can say which line keeps the site online.
The system is fine; the line is not. On a bad afternoon the counter waits and the staff go back to paper.
Releasing a fix means one engineer remoting in from a laptop. If that person is away, the fix waits.
The application and the database in a European region, with daily snapshots, HTTPS, and a bill you can read line by line.
One machine in the office for a system used only there, with a power backup, a fixed local address and a documented restore.
A push to the repository builds, tests and releases. The steps live in a file, not in someone's memory.
Uptime, disk space and certificate expiry checked from outside, with an alert that goes to a phone rather than an inbox nobody opens.
Fixed scope. Fixed price.
Agreed in writing before anything is built. You approve before we start.
Accounts, servers, domains and the actual traffic, starting with whoever deploys today — often the owner. Half the first meeting goes on finding out who holds the login.
Data residency, latency and the reliability of the office line point to different answers. We put the trade-off in writing before choosing. Algerian rules on hosting personal data are a legal question as much as a technical one: we describe what the system stores and where, and your lawyer confirms what is required.
The site first, then the database, then the scheduled jobs. Each step has a rollback that was tested, not one that was described.
A monthly figure you can predict, and a page that says what to do when it stops.
FAQ
What owners usually ask before requesting a quote for it.
Local is right when the system is used in one building, the data should stay in the country, and the office line is stable enough. Cloud is right when users are mobile, when load varies, or when nobody on site can restart a machine at eight in the morning. Most of our clients end up with both: a cloud site and a local system.
Hosting is usually a small line next to the domain, the database and the backups, and it depends on traffic and on whether you want a staging copy. We give the estimate before we build, and the bill is in your name so you can read it without asking us.
It depends on the design. A cloud-only system stops; a local server keeps working inside the building; a counter with an offline queue keeps selling and syncs later, at the cost of conflicts that have to be resolved. We will not claim offline tolerance a system does not have.
Yes. The accounts stay in your name, someone at your end has to receive an alert and be able to reach the office, and the monthly bill is yours to pay. We can run the infrastructure; we cannot be the only person who knows it exists.
Start a project
Send the brief. It comes back as a written scope and a fixed quote before anything is built.