Frequently Asked Questions

Install in your local systems /Thin client or Laptop having the 3D Application. Once installed successfully, please configure IP address in the Urja Connect.

Urja will send an automated email on your registered email ID.

Open 3D app > go to the preferences and switch on the Urja plugin from plugin manager.

Once Urja plugin is added successfully then it will show on menu taskbar of application.

The Master Account serves as the primary administrative account for a studio, while sub-accounts are secondary user profiles with controlled permissions, enabling secure and efficient team collaboration.

Yes, Urja Renderfarm integrates with standard production workflows and pipelines. Support for advanced pipeline tools such as ShotGrid is planned as part of Phase II enhancements.

Urja Renderfarm supports standard industry file formats used across leading DCC applications and render engines. A detailed list of supported formats is available in the user guide.

Yes, Urja Renderfarm supports the rendering of both still images and animation sequences, with scalable resources to meet production requirements.

You can run multiple rendering projects concurrently, subject to your selected top-up plan and available resource allocation. Resource availability follows a first-come, first-served basis.

Turnaround time depends on scene complexity, resolution, and the selected hardware configuration (CPU or GPU). Users can estimate and plan workloads using the pricing calculator available on the website.

Yes, new accounts receive 50 URC (Urja Render Credits) upon initial setup, allowing users to evaluate platform performance before committing to additional top-ups.

Yes, Urja Renderfarm can be accessed from any internet-connected device using registered studio credentials, provided the system meets the minimum supported operating system requirements.

Yes, rendering tasks can be paused, cancelled, or modified from the dashboard, depending on job status and account-level permissions.

A stable internet connection of at least 100 Mbps is recommended to ensure smooth asset transfers and responsive portal access.

Urja Renderfarm implements robust data protection measures, including encryption, role-based access controls, and secure infrastructure practices to safeguard project data. Urja is also TPN-Certified.

Yes, teams can collaborate using sub-accounts within the same studio environment. Storage access and permissions are managed by the administrator through the Master Account.

Failed tasks are highlighted in the job queue with detailed error logs. Users are advised to validate scenes locally and resubmit the job if required. For quick assistance, support is available via chat (L1), and tickets can be raised through the portal for further investigation.

Yes. Consumption data is updated in real time and can be viewed in the Job Details section under My Reports within the studio dashboard.

We support payments via the CCAvenue gateway for debit and credit cards. UPI payment options are also available for users in India.

Recharges are reflected instantly in the wallet and are visible in the account menu. Transaction history is available under the Recharge section. Paused jobs may resume automatically once sufficient credits are available. Failed jobs must be resubmitted by an authorized user.

Yes. Volume-based pricing and long-term plans are available for high-usage or bulk rendering requirements. Details are available on the pricing page.

Invoices are automatically generated for completed jobs and can be accessed and downloaded in real time from the billing dashboard.

Administrators can generate detailed consumption reports from My Reports, with filters such as date range, application usage, and sub-user activity.

If you are unable to purchase credits, please contact the support team by raising a ticket or initiating a live chat for immediate assistance.

During account creation, users may opt in or out of GST registration. If enabled, valid GST input credit is automatically applied to invoices.

Invoices are available in the billing dashboard. Admin users can filter invoices by period, user, or project.

If a GST or PAN number is not accepted, account creation cannot be completed. Please raise a support ticket with the relevant details for resolution.

Urja Renderfarm operates on a prepaid model. Users recharge their wallet with URC, and rendering costs are deducted based on hourly compute usage. Higher-value plans offer lower effective per-hour rates.

Use the Pricing Calculator to estimate costs based on frame count, timelines, and selected compute resources. The recommended plan is indicative and may vary depending on workload requirements.

Yes. All applicable taxes, including GST, are included in invoices in accordance with prevailing government regulations.

Render credits are generally non-refundable. Refunds may be considered only in exceptional cases, subject to review and approval based on a formal support request.

Billing begins when a render job is initiated. URC is deducted from the wallet in real time based on the compute resources consumed.

During account setup, you can designate a master administrator account and create sub-accounts. Administrators have full access to manage users, top-ups, permissions, and studio structure.

The platform uses a high-speed file upload and download accelerator for efficient asset transfers. The Urja connect application automatically scans assets. Auto-download options can be enabled or disabled from the portal.

Yes. Urja provides 24/7 support across multiple tiers, including live chat support and escalation to operations (Render Wrangling team) and engineering teams to ensure expert-level troubleshooting of complex render issues.

Yes. Rendering resources can be scaled on demand. Sharing project schedules in advance allows for effective capacity planning and SLA-aligned delivery.

Render nodes currently operate on Linux platforms. Users can access the portal from any supported operating system.

Rendered outputs are retained for 30 days after job completion. Email notifications are sent prior to deletion if enabled.

Task prioritization can be managed through the web portal. For urgent requirements, coordination with support teams or account managers is recommended.

Yes. Single-frame rendering is supported and is commonly used for testing, previews, and validation.

The master account has administrator-level permissions, while sub-accounts have restricted access based on assigned roles, enabling controlled collaboration.

Yes. Urja Renderfarm can be integrated into existing production pipelines with support from the technical team after initial test renders.

Urja supports major industry-standard formats based on the supported third-party applications and render engines available in the farm environment.

Yes. The platform supports both high-resolution still images and complex animation workloads using shared compute resources.

Concurrent job execution depends on your selected plan and available resources. Multiple jobs can run simultaneously within allocated limits.

Turnaround time depends on asset size, lighting complexity, render settings, and output resolution. Estimated completion times are visible in the portal after submission.

Yes. The web-based portal can be accessed from any internet-connected device, independent of the operating system.

Yes. Jobs can be cancelled or modified during execution. Credits for completed frames are non-refundable unless a verified technical error occurs.

Render time is calculated based on CPU or/and GPU usage, memory consumption, and processing duration. Influencing factors include file size, lighting complexity, render settings, and output resolution.

You can upload your complete project folder or packaged project file using Urja Connect or through the Web Portal.

Yes. Please provide all the required project dependencies, including plugins, Gizmos, Python scripts, Geo files, or any other external assets used by the Nuke project.

You can use Urja Connect for both upload and download of project data. 

No additional setup is required. The submission process is designed to be simple. You can upload the project package or project folder and then submit the Nuke file directly through the Web Portal.

You can monitor the job status and render progress through the Web Portal. Once the render is completed, the final output can be downloaded using the respective Job ID.

To initiate a Nuke Project POC, we request that you provide a valid Nuke 14.1v4 license or the corresponding version license used for your project. We also require all custom Gizmos, Nuke plugins, Python scripts (if applicable), geo/cache files, and any other project dependencies necessary for successful execution. Additionally, please share a sample Nuke project package that can be used for testing and validation purposes.

The recommended workflow begins with sharing the Nuke license and all required project dependencies. Once these are available, the project package or folder should be uploaded through Urja Connect or the Web Portal. After the upload is completed, the Nuke file can be submitted through the Web Portal for processing. The rendering job can then be monitored through the portal to track progress. Upon successful completion of the render, the output will be generated and made available for download using the corresponding Job ID.

Once we receive the Nuke license and all required dependencies, we can proceed with the POC setup. After the project data is uploaded successfully, the Nuke file can be submitted through the Web Portal, where the rendering job can be monitored until completion. The rendered output will then be available for download from the respective Job ID folder.

For the initial POC, we recommend starting with one representative Nuke project. This allows us to validate the complete end-to-end workflow, including project upload, dependency management, job submission, rendering, and output retrieval. Once the workflow is successfully validated, additional projects can be onboarded with greater confidence.