Customer relationship management (CRM) software holds the sales team's customer records, opportunities, quotes, and call notes. A field rep looks at the same record on a phone that an office colleague opens in a browser. When the server slows down, quotes do not go out and the customer card does not open when someone calls; if the database is damaged, years of customer history are gone.
We do not sell CRM software, and we give no licenses or functional support. Your organization picks the product. We run what sits underneath it: the server, database, network, backups, and security. We also do not host subscription CRMs that run in the vendor's own cloud. Our work is the infrastructure of CRM products that can be installed on a server of your own.
When you need it
- The CRM shares a server with the ERP, and at month-end close or during heavy reporting the sales team complains about slowness.
- The field team's mobile app connects to the server, but the server has been left directly open to the internet.
- Backups are taken, yet nobody remembers when a restore was last tried.
- The Outlook or IP telephony integration was set up once, and people fear it will break when the server is renewed.
- When a sales rep leaves, there is no way to see who exported customer data or who viewed which record.
- The user count has grown, but the server's processor and memory are still the size chosen at first installation.
The layers of CRM infrastructure
A CRM server is more than a single machine. Which layers are needed depends on the software and the number of users, and we check the versions it needs against the vendor's documentation before installing anything.
- The application and web server, the layer users reach with a browser.
- The database that holds customer, opportunity, and call records. The vendor sets the database engine; Logo Edge CRM requires SQL Server.
- Integration with the ERP: passing customer account and stock information between the two programs, either through the database or through a web service (REST).
- The mobile access point, the secure entry the field app connects through from outside.
- Email and telephony connections.
- Resources set aside for reports and dashboards.
Mobile app, email, and telephony connections
A CRM is one of the applications most exposed to the outside. Staff connect from phones in the field, from laptops at home, and from tablets in meetings. Field apps such as the Logo Edge CRM app pair with the CRM server's address when first set up, so the server must be reachable from outside. We design that access without leaving the server bare on the internet.
- Publishing. The mobile app reaches the web server from behind a web application firewall (WAF), which filters the requests sent to the application.
- Identity and access. We authenticate users with ARGE ZTNA or a VPN. We set up the certificate for the organization's domain name and renew it before it expires.
- Email. For the Outlook add-in and the Exchange connection, we open the server's access to the mail server and limit the permissions.
- Telephony. An IP telephony integration (CTI, computer telephony integration, where the computer and the phone work together) opens the customer card on screen when a call comes in. We do not provide phone numbers or voice services; we prepare the server environment where the IP telephony system and the CRM run.
Software that uses this infrastructure
For CRM products that have a page on our site, the infrastructure notes are on those pages. The points below rely on the vendors' own documentation.
- Logo Edge CRM is a separate product. The vendor does not require it to share a server with the ERP and prefers a server dedicated to this application alone. It asks for Microsoft SQL Server 2016 or later as the database. Depending on the package, it includes IP telephony integration, an Outlook add-in, and a REST service. It has no page of its own here; see the Logo infrastructure page.
- Canias CRM is the CRM module of Canias ERP. It works integrated with the ERP and can also be used alone. It has a mobile field app and telephony integration. For details, the Canias page.
- Workcube CRM shares a database with ERP and HR on the All in One platform. Besides sales-marketing and service-warranty modules, it has a Call Center module and CTI. Field sales uses a PWA, a web app that runs from the browser like an application. See Workcube.
- SAP Business One has opportunity, campaign, and service call functions, plus Outlook synchronization and the Sales and Service mobile apps. Page: SAP Business One.
- Mikro Fly is the only package listed with CRM in Mikro's package comparison. See Mikro Fly.
For the ERP side as a whole, go to ERP infrastructure.
Scope
- Server and database. We set up the application server and the database and apply updates after announcing them. We size processor and memory by the number of users, the field team's simultaneous connections, and the report load.
- Integration infrastructure. We prepare the server and network path where the data transfer between the CRM and the ERP runs. The business rules of the transfer are set by the software vendor.
- Backup. We back up the database regularly and write a copy to the isolated backup area on ARGE Cloud. We test a restore and report the result in writing.
- Access and security. We assign permissions by role and collect access logs in a central log system (SIEM). On the endpoint side we use XDR. The infrastructure is monitored 24/7; we settle in the contract who handles an alert and within what scope.
- High availability. If the software supports it and you want it, we build a setup in which a second server takes over when the main one fails. Whether it is needed depends on how well the sales team can tolerate downtime.
Backup and restore for CRM
In a CRM, loss usually comes from a record deleted by mistake or a faulty bulk update rather than from a major failure. So we design backups not only against a server crash but also to reach an earlier date. How far back to go, and for how long, we discuss with the organization; we do not impose a period.
Customer names, phone numbers, email addresses, and call notes in a CRM are personal data. The infrastructure side of Law No. 6698 on the Protection of Personal Data (KVKK) is ours to build, with role-based access, encryption, access logging, and an isolated backup. Our service alone does not meet your KVKK obligations. Managing marketing consents is the job of the organization and the software.
Head office, branches, and access from the field
Users at head office and branches reach the CRM in one of three ways, depending on your type of line.
- Your carrier's MPLS line. The provider joins head office and branches on its own private line.
- MPLS with a private link to ARGE Cloud. We extend the line to our cloud. Even when the CRM runs in the cloud, branch traffic reaches the server over a private line that does not touch the internet.
- IPsec when there is no MPLS. Over your existing internet lines, we set up an encrypted tunnel with SD-WAN capable routers and firewalls. SD-WAN manages several lines together.
For a salesperson in the field or someone working from home, we use ARGE ZTNA (zero trust network access: a user reaches only the applications they are authorized for) or a VPN. We never open the server directly to the internet. The line options are described in more detail under head office and branch connectivity.
Out of scope and limits
We do not sell CRM licenses, and we do not take on software configuration, field definitions, reports, or user training; we are not an authorized representative of CRM vendors. Consent for commercial messages and privacy notices are legal questions for your own counsel. Phone numbers, call routing, and voice services come from carriers; we only build the server environment for the telephony system. Subscription products that run in the vendor's own cloud are also outside our scope.
How we work
- We map where the CRM runs today, the number of users and field staff, the transfer with the ERP, and the connected telephony or email systems.
- We check the vendor's server and database requirements against its documentation, then send you a written design and capacity plan.
- Before moving, we back up and test restoring. We make the switch outside working hours and watch the mobile connection and telephony integration during the first days.
- We report backup results and resource use; how often is set in the contract.
Service models
Either way, the setup follows your organization. We look at what the software needs, your user and field team numbers, and the report load. We set processor, memory, disk, and network resources to your actual workload and plan capacity for growth.
- On ARGE Cloud: The CRM is hosted on our own infrastructure, which runs in a data center in Istanbul, inside a VPC reserved for you. On request we add a disaster recovery site, a second environment that carries on the work if the main system stops. You can do without it.
- In your own environment (on-premises): The server layout is designed and managed by us. If needed, we size the hardware and handle its purchase, and we work out the operating system and database licenses. After installation, we take on management, maintenance, and monitoring.
- Combined: The system runs at your site, and backups are kept in ARGE Cloud's isolated backup area.
Technologies we use: Windows Server · Linux · SQL Server · PostgreSQL · REST web services · Active Directory · MPLS · SD-WAN · IPsec · WAF · SIEM · XDR
Backups and the second environment are covered on the backup and disaster recovery page.
Frequently asked questions
Do you also provide the CRM software? No. You pick the software and buy the license from its vendor. We run the server, database, network, backups, and security. Field definitions, reports, and user support stay with the vendor.
Can the CRM and ERP share one server? It depends on the vendor. For Logo Edge CRM the vendor does not require it but recommends a server dedicated to the CRM. As load grows, a separate server shields the CRM from the ERP's reporting load. We decide together by looking at your user count.
Will the server be opened to the internet for the field team's mobile app? The app connects to the server's address from outside, so an access path is needed. But we do not open the server directly. We publish it behind a WAF, authenticate users with ARGE ZTNA or a VPN, and manage the certificate.
Do you set up the IP telephony integration? The integration itself is a setting of the software vendor. We prepare the network path and the environment where the CRM and telephony servers run. Numbers and voice service come from a carrier.
What do you do about KVKK for customer data? Only the infrastructure measures: role-based access, encryption, access logging, and an isolated backup. The organization decides on what consent the data is processed, how long it is kept, and how marketing consents are handled.