Her finner du en samlet, strukturert oversikt over hvordan GoRabbit fungerer – for kunder, tekniske brukere og governance/styring.
The proprietary internal mechanism handled automatically by the system.
RabbitEngine is the core execution proprietary internal mechanism handled automatically by the system. It analyzes campaign files, builds queues, determines posting times, interprets proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. It runs on both proprietary internal mechanism handled automatically by the system.
Builds queues, checks rules, and controls the publishing workflow.
RabbitEngine handles all background processes within the publishing workflow: reading campaign files (A/C files), generating pending-share queues, validating tokens and cookies, identifying group permissions, managing proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Multiple queues control the entire publishing lifecycle.
RabbitEngine uses a multi-layer proprietary internal mechanism handled automatically by the system. Each job is placed in the appropriate proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. Errors are moved to retry queues automatically, with all events logged in Slack.
To avoid suspicious patterns and restrictions.
Facebook detects patterns that differ from natural human behavior. If posts occur exactly every X seconds or in highly predictable intervals, the risk of restrictions increases. RabbitEngine therefore randomizes all intervals within safe boundaries to avoid suspicious patterns. This is one of the key reasons GoRabbit can publish to hundreds of groups without triggering safety mechanisms.
proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. If the account has little or no history in the group or if the group has strict moderation, it is automatically placed in WarmupQueue. The proprietary internal mechanism handled automatically by the system.
Failures move into retry queues and are attempted again.
If a publishing action fails — due to timeout, Facebook error, missing cookie, or temporary restriction — it is automatically moved to FailedQueue or RetryQueue. RabbitEngine retries after a defined and randomized proprietary internal mechanism handled automatically by the system. The system automatically halts after a certain number of failures to avoid tripping Facebook’s safety mechanisms. All retry events are logged in Slack for full traceability.
proprietary internal mechanism handled automatically by the system.
RabbitEngine sends all important events to dedicated Slack channels using Webhooks. This includes proprietary internal mechanism handled automatically by the system. Slack acts as a real-time monitoring system that provides full visibility without requiring manual server log inspection.
proprietary internal mechanism handled automatically by the system.
RabbitEngine immediately halts queues showing signs of serious deviation, such as empty tokens, invalid cookies, 302 redirects, unexpected Facebook HTML changes, or infinite loads. When this occurs, a critical warning is sent to Slack. The system requires manual operator intervention to continue, preventing major issues such as account-wide blocking.
Generates natural times using randomized intervals.
Posting timestamps are generated based on campaign rules, segment priority, group history, and proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. The system avoids tight sequential posting to minimize Facebook restriction risks. The schedule is stored directly in the proprietary internal mechanism handled automatically by the system.
Reads A-files, C-files, mappings, segments, proprietary internal mechanism handled automatically by the system.
RabbitEngine reads several JSON files including: campaign files (A-files), pending share rules (C-files), group mappings, segment definitions, proprietary internal mechanism handled automatically by the system.json, and system config. These files make the proprietary internal mechanism handled automatically by the system. All files reside in defined paths under the RabbitEngine directory in GoRabbitStudio.
Generates queues, retries, proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. These files are used by the proprietary internal mechanism handled automatically by the system. The output files are structured so they can be debugged without reading proprietary internal mechanism handled automatically by the system.
Yes — fully platform-agnostic.
Yes. The proprietary internal mechanism handled automatically by the system. It functions identically on Linux-based proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. The only differences are OS-specific path formats.
Monitors proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. If any abnormal pattern is detected, the system halts automatically to prevent escalation. Fail-safes include auto-halt, auto-retry, Slack alerts, and full validation of all input files before execution.
Very easy to extend with new modules.
The proprietary internal mechanism handled automatically by the system. Future modules like TikTok or LinkedIn can be added by extending the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
State stored continuously in proprietary internal mechanism handled automatically by the system.
RabbitEngine is designed to stop and start safely without data loss. All progress is stored in JSON-based proprietary internal mechanism handled automatically by the system. Each publishing job has its own status variable, and the proprietary internal mechanism handled automatically by the system. This makes long-term operation stable and traceable.
Built with minimal dependencies.
The proprietary internal mechanism handled automatically by the system. Core functionality is written in pure Python, using only minimal libraries such as requests and json. This keeps the proprietary internal mechanism handled automatically by the system. All advanced operations are delegated to RabbitAgent to keep the proprietary internal mechanism handled automatically by the system.
Continuously validates group access.
RabbitEngine cross-checks group IDs across multiple data sources: campaign files, proprietary internal mechanism handled automatically by the system. If a group has been deleted, changed, or access has been removed, the group is marked inactive and removed from the pending-share proprietary internal mechanism handled automatically by the system. This prevents the proprietary internal mechanism handled automatically by the system.
Binds segments to the correct groups.
The proprietary internal mechanism handled automatically by the system. This uses a combined rule proprietary internal mechanism handled automatically by the system. The result is a precise list of groups the campaign should target. Segment binding is the foundation of targeted publishing.
JSON enables flexible and robust architecture.
JSON makes GoRabbit platform-independent, flexible, and extremely easy to integrate with frontend, backend, APIs, and proprietary internal mechanism handled automatically by the system. It is readable by both machines and humans, easy to validate, and simple to version-control in Gitea. With JSON, all modules communicate without being tightly coupled. This creates a robust architecture with minimal complexity and maximum transparency.
Errors halt, are fixed, and resume without loss.
The proprietary internal mechanism handled automatically by the system. Once the operator fixes the issue (new cookie, refreshed proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system. The entire system is built for safe recovery.
Adapts to all Facebook limits and restrictions.
The proprietary internal mechanism handled automatically by the system. Based on this, it adjusts intervals, halts queues, or retracts risky jobs. In cases of suspected algorithmic surveillance, the proprietary internal mechanism handled automatically by the system. This protects both the account and the campaign.
Yes — full parallel support.
Yes. The proprietary internal mechanism handled automatically by the system. Each campaign generates its own proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This makes it possible to run 3–10 campaigns simultaneously without conflict.
Campaigns prioritized by rule system.
Each campaign can be assigned priority via segments or customer-specific rules. The proprietary internal mechanism handled automatically by the system. Additionally, the system may slow down lower-priority campaigns if Facebook safety conditions require it. This ensures critical campaigns always run first.
Very lightweight and resource-efficient.
The proprietary internal mechanism handled automatically by the system. It uses minimal CPU and almost no RAM because it primarily operates on small JSON files and limited computations. The heavy part of the system — actual posting — is delegated to RabbitAgent. This makes the proprietary internal mechanism handled automatically by the system.
Validates tokens and cookies before execution.
The proprietary internal mechanism handled automatically by the system.json and from RabbitAgent session directories. It validates that tokens have not expired and that cookies still function as authentication. If anything is invalid, the proprietary internal mechanism handled automatically by the system. Tokens and cookies are never shared outside the server.
Combines master list + customer proprietary internal mechanism handled automatically by the system.
Resolved proprietary internal mechanism handled automatically by the system.json. The result is stored as gruppe_mapping_resolved.json. This proprietary internal mechanism handled automatically by the system. This step ensures full flexibility without losing original master data.
proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. 2) Resolve mappings. 3) Bind segments. 4) Generate queues. 5) Determine posting times. 6) Run proprietary internal mechanism handled automatically by the system. 7) Push jobs to RabbitAgent. 8) Monitor execution. 9) Handle errors and retries. 10) Log everything to Slack. This structure makes the system easy to extend.
Idle mode monitors and waits.
When no campaigns are active, the proprietary internal mechanism handled automatically by the system. It waits for new proprietary internal mechanism handled automatically by the system. It monitors tokens, checks proprietary internal mechanism handled automatically by the system. Idle mode uses almost no resources, making the system energy-efficient and ready to respond instantly.
Yes — modular for multiple platforms.
Yes. The architecture allows adding new module agents for TikTok, LinkedIn, Instagram, and X. The proprietary internal mechanism handled automatically by the system. The JSON-based interface makes it easy to extend without modifying the core.
Debug via Slack, JSON queues, and terminal.
proprietary internal mechanism handled automatically by the system. 2) JSON proprietary internal mechanism handled automatically by the system. 3) Terminal output when the proprietary internal mechanism handled automatically by the system. Because everything is proprietary internal mechanism handled automatically by the system.
Versioned in Gitea with full history.
proprietary internal mechanism handled automatically by the system. Each update to proprietary internal mechanism handled automatically by the system.Y”. JSON input files have their own versioning and are independent of the proprietary internal mechanism handled automatically by the system. This allows upgrading the proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
Core directory paths include: includes/ (proprietary internal mechanism handled automatically by the system. The structure makes everything easy to locate and debug without searching through the entire project.
All proprietary internal mechanism handled automatically by the system.
All communication is proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. No sockets or network protocols are used, making communication extremely stable and easy to debug — no bottlenecks or network failures.
Only Python 3 and proprietary internal mechanism handled automatically by the system.
RabbitEngine only requires Python 3 and proprietary internal mechanism handled automatically by the system. It does not depend on databases, API keys, or heavy third-party libraries. This makes the system extremely easy to deploy on both Linux proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Stop via SIGTERM or stop proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. When the operator sends SIGTERM or creates a stop proprietary internal mechanism handled automatically by the system. This is safer than killing the process directly, as proprietary internal mechanism handled automatically by the system.
Auto-adjustment during rate-limits.
If Facebook signals that the account is hitting volume limits, the proprietary internal mechanism handled automatically by the system. The system may also distribute posting over longer time periods to reduce load. As a result, rate limits are rarely triggered in practice.
Crash-safe with multiple fail-safes.
The proprietary internal mechanism handled automatically by the system. If a single job fails, the entire proprietary internal mechanism handled automatically by the system. If a proprietary internal mechanism handled automatically by the system. If the whole system is at risk, a global fail-safe activates and stops everything. JSON-based state allows the proprietary internal mechanism handled automatically by the system.
Consumes very little RAM.
RabbitEngine is extremely memory-efficient. Most operations involve reading and writing small JSON files, which require minimal RAM. Even for large campaigns with hundreds of groups, memory usage typically stays well below 200 MB. Because the heavy lifting (browser automation) is handled by RabbitAgent, the proprietary internal mechanism handled automatically by the system.
CPU usage is typically under 3%.
CPU consumption is very low. The proprietary internal mechanism handled automatically by the system. This keeps CPU usage typically between 1% and 3% on a normal proprietary internal mechanism handled automatically by the system. Only during heavy proprietary internal mechanism handled automatically by the system.
Updated via Gitea and restart.
The proprietary internal mechanism handled automatically by the system. New versions are pulled or merged, and the proprietary internal mechanism handled automatically by the system. Because all state is stored in JSON files, no progress is lost during the update. Updates can also be tested in a staging directory before going live. This ensures safe upgrades with minimal downtime.
Logs stored in Slack + proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. These may include event logs, error logs, proprietary internal mechanism handled automatically by the system. Slack acts as the main monitoring system due to real-time visibility. proprietary internal mechanism handled automatically by the system.
Yes — multiple tokens supported.
Yes. The proprietary internal mechanism handled automatically by the system. This enables publishing for multiple businesses or pages within the same campaign cycle. The proprietary internal mechanism handled automatically by the system. This adds high flexibility for multi-client setups.
Yes — very low risk of memory leaks.
Yes. Because the proprietary internal mechanism handled automatically by the system. Additionally, the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
When the server restarts, all proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This ensures no publishing progress is ever lost. The only requirement is that RabbitAgent is restarted so publishing can continue normally.
Single-threaded for stability.
The proprietary internal mechanism handled automatically by the system. Multithreading is only used in helper functions that don’t affect core state. Heavy concurrency is delegated to RabbitAgent, which manages multiple browser sessions.
Dry-run = simulation. Live-run = publishing.
Dry-run is a simulated execution where the proprietary internal mechanism handled automatically by the system. Live-run means jobs are actually passed to the proprietary internal mechanism handled automatically by the system. Dry-run is always run first to ensure the campaign is correctly configured before publishing begins.
No technical limits — follows Facebook’s boundaries.
No. There are no hardcoded limits in the proprietary internal mechanism handled automatically by the system. The only limits come from Facebook’s security policies. The proprietary internal mechanism handled automatically by the system. The system can handle anything from small campaigns to several thousand posts per week.
Automatically halts on unusual patterns.
Autopause is an intelligent safety feature that automatically pauses publishing if the proprietary internal mechanism handled automatically by the system. The system instantly alerts Slack so an operator can investigate before publishing resumes.
Simplicity, modularity, transparency.
RabbitEngine follows the principles of simplicity, modularity, and full transparency. All state lives in files, with no dependency on complex databases or external systems. Each module has a single responsibility. Click-for-click publishing is separated from planning (proprietary internal mechanism handled automatically by the system. The system is built to be robust, testable, documentable, and safe to upgrade.
The intelligent proprietary internal mechanism handled automatically by the system.
RabbitEngine is the stable, safe, and intelligent motor that plans and controls all publishing within GoRabbit. It builds queues, analyzes rules, mimics human behavior, monitors risk, handles errors, protects accounts, and collaborates with RabbitAgent to execute the actual postings. Without the proprietary internal mechanism handled automatically by the system.