Site · Site operations
Run finished sites end to end: manage domains, publishing, and search visibility so every site keeps serving your business.
Product enquiry · confirm access conditions
Getting started
- Define the goal: Site · Site operations
- Agree on scope: Domains and certificates
- Validate agreed outcomes before use or handover.
A process illustration, not a customer case study. Confirm scope, features, and terms against the actual product or service agreement.
Core capabilities
- Domains and certificates
- Publishing and rollback
- Search visibility and visitors
Industries: Cross-industry · Retail & trade · Professional services
Integration and deployment
Check where the product can run, how it stores data, and what network access and integration it needs. A catalog listing does not mean the app is already set up or works in every environment.
Business systems, ready for private deployment.
Choose a subscription or deploy business systems on company-managed servers or private clouds and connect to Runlume. Manage business databases independently and exchange data through explicit grants. System collaboration and Agent calls respect tenant and permission boundaries.
Software licensing, deployment, implementation, maintenance, upgrades, platform services, and resource usage for private deployments follow the selected agreement.
Explore local deployment and data protectionService scope
These are product capabilities. Your selected plan or service agreement determines delivery scope, available features, and resource allowances.
Explore capabilities and workflowsBefore you purchase
- Plan features, account, and instance scope
- Price, validity, allowances, and renewal terms
- Provisioning, support, and after-sales terms
From launch to ongoing operations.
How do Site and CMS work together?
Site handles domains, publishing, search visibility, and visitor operations; the site build itself is delivered by the project completed before onboarding. CMS organizes articles, product information, and brand materials. They connect through agreed interfaces; define which content appears, when it is published, and how updates reach the site during integration.
What should a business prepare before launching its website?
Prepare brand materials, product and service descriptions, contact entry points, and text and images you have rights to use. Confirm the domain, hosting, and publishing owner. For visitor data or third-party analytics, define the purpose, handling, and notices. Site build, content, and deployment work follow the selected scope.
Can website enquiries be handed over to CRM?
Authorized lead fields can be passed to CRM under the integration plan. Define the receiving system, field mapping, customer matching, and follow-up owner, then verify failed submissions and duplicate handling. Launching a website or buying both apps does not itself establish data sharing.
Next, check the fit for your business.
Check where the product can run, how it stores data, and what network access and integration it needs. A catalog listing does not mean the app is already set up or works in every environment.