You
- You provide the server and the network, and IWB runs on your server.
- The database, files, and backups stay on your server.
- You add regular and off-server backups to your own backup routine.
- You decide whether to turn on automatic updates.
On-premise
Your data stays on your own server
The database, files, and backups live on your server. Our team installs IWB with you, and you get the same modules and user permissions as in the cloud.
01
Who on-premise is for
We designed the on-premise option for the situations below. If you'd rather not run a server, you can use IWB in the cloud.
Organizations that keep data in-house
If your policy requires business data to stay on your own servers, IWB runs there too.
Networks with limited internet access
If your servers sit on a network with restricted internet access, IWB can run there. Below, we list which tasks need the internet.
Companies with their own IT team
If your IT team already runs your servers, IWB becomes part of your existing infrastructure and backup routine.
02
Who handles what
The server and the data stay with you. We plan the installation and the update schedule together.
The IWB team
- We handle the installation and its settings together with you.
- We provide a license file for your installation. The license is validated on your server without an internet connection.
- We agree on the update schedule and maintenance window with you.
- We offer optional automatic updates: the database is backed up before updating, and you don't need to open inbound access to your server.
03
When you need the internet
The license is validated offline. You need the internet for installation and updates, exchange rates, the secure connection certificate, and any external services you turn on.
- No internet needed
License validation
The license is validated on your server without going online.
- Needs internet
Installation and updates
The new version is downloaded from the internet at installation and with each update. Automatic updates connect only outbound from your server.
- Needs internet
Exchange rates
IWB fetches daily exchange rates from the Central Bank of the Republic of Turkey (TCMB).
- Needs internet
Secure connection certificate
Needed if the certificate is obtained and renewed automatically. Not needed if you use your own certificate.
- Needs internet
AI and integrations
Needed only for the services you turn on: IWB AI, your e-document integrator, email and SMS, and bank transaction feeds.
- No internet needed
Usage statistics and error reporting
Off unless turned on for your installation. IWB works without them.
04
Whichever you choose, you get the same modules
User permissions are the same in both, too. What differs is the setup, the web address, updates, and where your data lives.
| Area | Cloud | Your own server |
|---|---|---|
| Setup | We set up your workspace | On your server, together with our team |
| Web address | yourcompany.iwb.com.tr, or your own domain if you prefer | Your own domain |
| Updates | We handle them | We agree on the schedule and maintenance window with you; automatic updates are optional |
| Database and files | On servers we operate | On your server, along with the backups |
| License | Modules are turned on according to your plan | A license file issued to you, validated without an internet connection |
| Sign-in page | Company name, logo, color, and welcome message | Your workspace name and branding |
| Product | Same modules and user permissions | Same modules and user permissions; web address and sign-in page settings are cloud-only |
05
For your IT team
We share the system requirements and installation details with your IT team during the demo and quote process.
- The database, files, and backups are kept together in a data folder on the server. You back up and move servers through that folder.
- Management needs no inbound connection to the server. Automatic updates make only outbound, encrypted connections.
- To install updates, the automatic updater runs with privileged access on the server. It shares operational data such as version, system health, disk, and backup status with our team.
- Data separation between workspaces is enforced at the database level as well as in the application. A security check runs at every startup.
- External services such as usage statistics, error reporting, and AI run only when they are turned on.
06
Frequently asked questions
What are the system requirements?
We share the system requirements and installation details with your IT team during the demo and quote process. We size the server with you based on your number of users.
Who handles updates? Are they automatic?
We agree with you on the update schedule and maintenance window for your installation. Automatic updates are optional. When they're on, a database backup is taken first, then the new version is installed and the system is checked to confirm it's running. If you stop automatic updates, no new versions arrive.
Does your team connect to our server?
No inbound connection to your server is opened for administration. If you turn on automatic updates, your server makes only outbound, encrypted connections. Operational information such as version, system health, disk, and backup status is then shared with our team. To install new versions, the automatic updater runs with privileged access on your server.
What happens if our license expires?
You keep access to your data. When the license expires, IWB keeps working fully during a grace period, with a warning banner on screen. After the grace period ends, you can't turn on new modules, but the modules you already use keep working.
Who takes care of backups?
Regular backups, and backups kept off the server, are your IT team's job. The database and files sit in the same data folder on your server; your team adds that folder to its own backup routine. If automatic updates are on, a database backup is also taken before every update, and the last 5 backups are kept on your server.
Can we run multiple companies and workspaces on our own server?
Yes. You can open multiple workspaces in your installation and set up multiple companies and branches in each one. Data separation between workspaces works the same way as in the cloud: data is kept apart in both the application and the database.