Run Sembot on your own infrastructure with your own API keys for LLMs and video generation. No Sembot licence limits and no commission on API usage — scale is determined by your infrastructure’s performance.
Try the task workflow first. In the consultation, we will scope infrastructure, integrations and deployment.
Choose which external services to connect.
Start with one project and a representative task. This scope lets you check connections, the way people and AI work together, and operational responsibilities before extending the environment across your organisation.
Identify where Sembot will run, who will use it and how they need to connect. List the advertising accounts, data sources and AI providers the application needs. Use this scope to agree infrastructure requirements and network connections.
Prepare your LLM and video provider accounts and the permissions required by your integrations. Share keys through the agreed configuration channel. Assign responsibility for provider billing and for operating the environment.
Run the chosen process, review its task and try an available way to resolve it. Check integration behaviour and the cost of the services used. Then define the next projects and the resources needed to support them.
Run an isolated Sembot environment on any infrastructure that meets agreed requirements. Professional imposes no licence limits: size the environment to its workload. External connections also remain subject to API providers’ limits and availability.
Connect your own API keys for LLM and video-generation providers. You pay the provider directly for API usage at its rates. Sembot adds no commission or markup to that usage; the provider’s usage charges remain yours to pay.
Restrict network access to your organisation’s users. Advertising APIs, LLM and video providers and notification channels need a separate outbound traffic plan. Isolating the application does not disconnect those services.
Add White Label to offer the platform under your own brand and domain, and portfolio management when you need a shared overview of projects and your team. Before launch, we will agree on the environment operator, data access, backups and updates.
Professional has no licence limits on products or projects. Size infrastructure for process frequency and concurrent work. External API limits and availability still depend on their providers, so account for those constraints when planning workloads.
Treat the Professional licence, infrastructure and external API usage as separate budget items. Pay LLM and video providers directly. Sembot adds 0% commission or markup to that usage. Optional add-ons are scoped separately.
A VPN can restrict application access. White Label lets you agree how to offer it under your brand; portfolio management supports work across projects. These add-ons do not replace decisions about access and who operates the environment.
Professional can run on any infrastructure that meets the agreed requirements. We will review integration, access and operational needs before deployment. Choose a configuration that fits the workload and the way your team works.
Application access can be private. Advertising APIs, external AI models and notifications need appropriate outbound connections. Include those dependencies in the network design.
We agree the operator, responsibilities, update process and recovery arrangements before deployment. Bring your IT requirements so they can be included in the scope.
Choose one project, process and group of pilot users.
Describe the infrastructure, access requirements and AI providers; do not send keys through the form.
List your requirements for operations, White Label and portfolio management.
Prepare details of your infrastructure, LLM/video providers and access requirements. The consultation defines deployment scope, operations ownership and the next step — without sending API keys through the form.
