Skip to main content
New release Β· v8.4.0

RTILA X 8.4.0 is here

Every feature reviewed and refactored, plus a long list of fixes. Here is what you get:

  • AI that works without your own key AI Self-Correction and AI Completion now run on shared RTILA AI, in desktop, scheduled, remote and bot runs.

  • Cloud and Remote mode run your projects Projects and trigger chains now execute in Cloud and Remote mode. Stopped runs keep their checkpoint and can be resumed.

  • Proxies with a login, in any Chromium browser Authenticated proxies now work everywhere, including Google Chrome, and side requests follow the run’s proxy.

  • Redesigned Visual Builder The side panel opens by itself, fits any width and gives empty projects a clear first step.

Free forever plan Β· No account needed Β· Already using RTILA X? Check the β€œBehaviour changes” section in the notes before updating.

Keep Every Product Version Under Control

Manage source projects, exported builds, and client updates from one organized workflow.

From One Product to a Product Line

Your first exported bot may be simple: source project in one folder and a zip file in another. As you build more products and deliver more client versions, that simple system becomes harder to manage. Which client received version 1.4? Which source project produced the latest macOS build? Those questions matter when updates and support requests arrive.

RTILA X supports organized bot management by keeping source automations inside the project system while you control exported files and delivery records. The application itself does not impose a rigid inventory database, but the local project structure makes it easy to maintain clear naming and version notes.

Source Projects and Build Versions

The source project remains the single source of truth. When you need to improve the automation, you edit the source workflow and compile a new build. You can include version information in the export name or in the bot’s branding, such as PriceMonitor-1.5-win.zip.

Maintaining consistent naming and a simple changelog helps you answer client questions quickly. You know exactly which build a client received and what changed in each version.

Updating Client Deliveries

When a site changes or you add a feature, clients need the updated bot. Because the source project stays in RTILA X, you can compile the same workflow again with the new improvements and distribute the replacement file. Client branding and access protection settings can be reapplied at export time.

Updates are the most practical form of ongoing client value. They give you a reason to maintain the relationship and potentially offer annual support plans or premium feature tiers.

Organizing Your Export Library

You can store exported files in folders arranged by client, product, or platform. Alongside each export, keep a small notes file with the version number, delivery date, and any special credentials or branding. This simple practice prevents confusion as your product line grows.

Because RTILA X operates locally, your export library stays private and under your control. You are not dependent on a hosted marketplace or vendor dashboard to manage your products.

Frequently Asked Questions

Can I update a bot after it is delivered?
Yes. Improve the source workflow, compile a new version, and distribute the updated executable to clients.
Does RTILA X track which users received which version?
RTILA X helps you organize exports locally. You can maintain your own delivery notes for client-specific versions.
Are compiled bots stored with their source projects?
You can keep exported files in organized local folders and associate them with their source projects.

Ready to Get Started?