--- title: "1С:Предприятие 8.3 ПРОФ vs КОРП: Key differences and when to migrate" url: "https://cybernetica.kz/en/blog/10" description: "A technical comparison of 1С:ПРОФ and КОРП covering session and CPU core limits, fault tolerance, security, and when to migrate to the corporate edition." --- # 1С:Предприятие 8.3 ПРОФ vs КОРП: Key differences and when to migrate A technical comparison of 1С:ПРОФ and КОРП covering session and CPU core limits, fault tolerance, security, and when to migrate to the corporate edition. ## Article ## 1С:Предприятие 8.3 ПРОФ vs КОРП: Key differences and when to migrate Choosing between license editions of the 1С:Предприятие platform is a strategic step for a growing business. As a company scales, the ПРОФ edition can become a physical barrier to growth. This article examines the technical differences between 1С:Предприятие ПРОФ and КОРП and explains the risks of using the basic edition in high-load systems (HighLoad). ## 1. Hardware limits: the “glass ceiling” of scaling These parameters are embedded in the license protection code and strictly checked by the platform when user sessions start. **User limit**: The ПРОФ edition allows no more than 500 concurrent sessions. Once the number of active sessions reaches 500, the 501st employee cannot log in. The КОРП edition operates without this limit. **Server capacity usage (CPU cores)**: One worker process (rphost) in the ПРОФ edition can use up to 12 CPU cores. With 24 cores and one process, half the capacity remains idle. The КОРП edition uses all available cores without restriction. ## 2. Stability under high load (HighLoad) To address performance in high-load systems, the КОРП edition provides critical administration settings. The ПРОФ edition prohibits changes to these settings and uses a value of “0”. **Workload isolation (Function assignment)**: This is the most important tool for high-load systems. It physically separates different task types across servers or processes. In КОРП, an administrator can assign “Server A” only to client connections and “Server B” only to background jobs. In ПРОФ, every cluster server performs all tasks together. **Memory management (RAM)**: КОРП lets administrators set “Safe memory consumption per call” so one heavy report does not crash a worker process. In ПРОФ this limit is 0, which can crash the entire worker process and disconnect all its users after a faulty query. **Worker process granularity**: КОРП can limit the number of users in one operating-system process, for example to 50. It can also place different information bases, such as a heavy 1С:ERP base and a light 1С:Бухгалтерия base, in separate processes. ## 3. Fault tolerance and business continuity (24/7) In the corporate sector, downtime translates directly into financial losses. **Fault-tolerance level**: КОРП allows a specified number of backup servers in a cluster. If one server fails, a backup automatically takes over its sessions. The fault-tolerance level in ПРОФ is always “0”. Failure of any worker server completely stops all users assigned to it, with no automatic reconnection. **Background database updates**: КОРП can change database table structures without stopping users. In ПРОФ, configuration updates require exclusive access and all users must log out. On large databases, this can take 5–10 hours. **Automatic process restart**: КОРП can configure a restart interval and allowed memory volume to “softly” replace a process without interrupting connections. ## 4. Administration of geographically distributed networks For companies with branches or many remote employees, КОРП mechanisms radically reduce the IT department's workload. **Thin client updates**: In ПРОФ, updates work through a shared network folder (SMB) or require manual installation, which is unsuitable for remote employees without direct local-network access. КОРП can automatically distribute thin-client updates via HTTP/HTTPS directly from the 1С web server. **Centralized database list**: In ПРОФ, users must enter the database path manually or copy the ibases.xml file. In КОРП, the database list is published on a web server and changes immediately appear for all employees through one URL. КОРП can also provide different database sets to different user groups. ## 5. Information security: operating-system access risk The least visible but most dangerous issue for the corporate sector. The ПРОФ edition has no sandbox. Code has the full rights of the 1С service's system account. ПРОФ will execute malicious code from an external processing module that can copy server files or scan the internal network. The КОРП edition provides **Security profiles (Security Sandbox)**. Administrators can prevent code from accessing files on server disks, reaching specified internet addresses, or launching external components (DLL/COM). This provides reliable protection from programming errors and malicious processing modules. **Technical parameter** **1С:Предприятие ПРОФ** **1С:Предприятие КОРП** Cluster session limit 500 Unlimited CPU core limit per process 12 Unlimited Memory limits (RAM) Prohibited (0 only) Available Sessions/databases per rphost Prohibited (0 only) Available Fault-tolerance level 0 only Any value Function assignment Unavailable Available (flexible configuration) Background updates Unavailable Available Security profiles Unavailable Available External session management Unavailable Available Thin client updates Via local network / manually Via HTTP/HTTPS (automatically) ## 6. Technical differences explained: What do they mean for the business in plain language? If a system administrator says the ПРОФ edition “prohibits editing RAM limits,” the business faces a risk that the entire office may suddenly stop working. Below, we translate complex technical restrictions into real business situations. ### 📈 Scaling and server utilization ### Session limit (500 users) **In the ПРОФ edition:** A hard limit of no more than 500 concurrent sessions applies. **In plain language:** Once 500 people are active in the database, the 501st employee cannot log in. For a large company, this risks paralyzing an entire department or branch during peak hours. КОРП has no such limitation. ### CPU core usage (up to 12 cores) **In the ПРОФ edition:** One worker process can use a maximum of 12 server cores. **In plain language:** You can buy a powerful server with 24 or 64 cores for millions of tenge, but ПРОФ will use only a small part of its capacity. The database will slow down even though the server is almost idle. КОРП uses 100% of the hardware you purchased. ### 🛡️ Stability and failure protection (HighLoad) ### Editing memory limits (RAM) **In the ПРОФ edition:** Memory management settings are locked at “0”. **In plain language:** If one accountant starts generating a huge, complex report, the query can consume all server RAM without control. The server may then crash and **all 500 users will be disconnected at once** with unsaved data lost. КОРП acts as an intelligent circuit breaker: it forcibly stops that one heavy report, while the other 499 people continue working without interruption. ### Session limit per worker process (rphost) **In the ПРОФ edition:** The platform decides how to group users, and administrators cannot configure it manually. **In plain language:** In ПРОФ, all employees are in one large “boat.” If a software error sinks it, everyone goes down. КОРП can place users in small isolated “boats,” for example exactly 50 people each. If a failure occurs, only 50 people are disconnected rather than the entire company, limiting the incident's impact. ### ⏳ Business continuity (24/7) ### Fault-tolerance level **In the ПРОФ edition:** It equals “0”; there is no redundancy. **In plain language:** If the physical server fails, the entire company stops until it is repaired. КОРП can use backup servers. If the primary equipment fails, the database automatically and transparently switches all users to a backup node. ### Function assignment (Workload separation) **In the ПРОФ edition:** Server tasks are mixed together. **In plain language:** Heavy scheduled operations, such as month-end closing or cost calculation, can consume every resource and paralyze sales managers or cashiers. In КОРП, administrators can specify: “This server handles only users, while that server handles only heavy background calculations.” ### Background updates **In the ПРОФ edition:** All employees must be logged out of the database. **In plain language:** A software update means several hours of complete downtime for a store or warehouse. КОРП can update table structures “in the background” while people continue entering documents. ### 🔐 Security and remote employee administration ### Security profiles (Sandbox) **In the ПРОФ edition:** Any program code has full system rights on the server. **In plain language:** This is a major security vulnerability. A dishonest programmer or contractor can write code that secretly downloads confidential files from the server or introduces a virus into the corporate network. КОРП places all code in strict isolation, a “sandbox,” so it physically cannot leave 1С and access the operating system. ### External session management **In the ПРОФ edition:** Unavailable. **In plain language:** In КОРП, the cluster can call an external web service, such as an administrator's separate central database, to decide whether to start a session. Holdings can centrally manage license quotas, for example no more than 300 licenses for ERP and 50 for ЗУП, deny access outside working hours, or block specific client types (web/thin) without changing configuration code. ### Thin client updates via HTTP **In the ПРОФ edition:** Updates are installed manually or through the local network. **In plain language:** When remote employees lack office-network access, every 1С update becomes a nightmare for the system administrator. КОРП solves this: remote employees' 1С installations download and install updates directly over the internet (HTTP), as easily as smartphone application updates. The correct database list is also updated automatically for everyone. ## Summary: When does migration to КОРП become unavoidable? Using ПРОФ in a large business means the system is operating at the limit of its architectural capabilities. Your company should consider a license upgrade if: • The number of users during peak hours is approaching the limit of 500 concurrent sessions. • You invested in modern high-performance servers, but ПРОФ uses no more than 12 cores per worker process, creating an artificial performance shortage. • Heavy reports launched by individual employees cause memory shortages, worker-process failures, and mass disconnection of all users. • Database update maintenance windows require a complete shutdown with exclusive access for several hours, paralyzing shipments and production. • Commercial secrets and servers require strict protection from unauthorized access through third-party code using security profiles. ## 🎯 Order a free audit of your 1С:Предприятие system Unsure whether your current 1С infrastructure uses all the capacity of your purchased servers? Tired of database slowdowns during month-end closing and interface freezes? Engineers and architects at **Cybernetica** will conduct an in-depth technical audit of your 1С system to determine: • Whether the current cluster and hardware configuration contains bottlenecks. • Hidden data-loss risks and causes of recurring downtime. • The feasibility and return on investment (ROI) of migrating your company to 1С:КОРП. ## Access for AI agents (MCP) **Cybernetica MCP server:** `https://mcp.cybernetica.kz/mcp` Connect this endpoint as an MCP connector in Claude, ChatGPT, Cursor, or another Model Context Protocol client for direct structured access to all company data — the product catalog, client cases, pricing, blog posts, and vacancies — with full-text search and no HTML parsing. Access is public, read-only, and requires no authentication. The Markdown language is selected by the page URL: Russian has no prefix, Kazakh uses `/kk`, and English uses `/en`. Send `Accept: text/markdown` to that URL or pass its path to `/api/agent-markdown?pathname=...`. The public REST API accepts `?locale=ru|kk|en`; Russian is the default. The MCP server tools take the same optional `locale` argument: if a record has no translation into the requested language, it comes back in Russian with a note saying so. ### Other resources for agents - [API catalog](https://cybernetica.kz/.well-known/api-catalog) - [OpenAPI](https://cybernetica.kz/api/openapi.json) - [LLMs.txt](https://cybernetica.kz/llms.txt)