Loading page…
Make institutional computing resources easier to share and operate. Curobotic’s shared research computing solution brings project access, application environments and resource policies into one defined service for researchers and administrators.
How the solution fits together
Agree project eligibility, allocation rules and institutional ownership.
Connect users to applications, queues and project data.
Establish onboarding, maintenance, reporting and a support route.
Inside the solution
A shared facility needs rules for admission, sponsorship, quotas and acceptable use. We help translate the institution’s decisions into an operating model with named owners. Funded projects, teaching allocations and exploratory work can have different access arrangements, but those distinctions should be understandable to the people submitting jobs.
Researchers may need terminals, batch submission, notebooks or remote visual applications. The platform scope selects appropriate access routes and integrates the agreed identity source. A browser portal can simplify common tasks, while controlled administrative access remains separate. User onboarding should include a small example that demonstrates the intended workflow.
Each project needs a way to select software, find shared data and retain outputs. We define environment ownership, storage locations and the handling of inactive accounts. Quotas and retention policies are visible to users. Backup coverage is explicitly assigned to data classes so researchers know which working directories are temporary.
Queue information, capacity trends and incident records help the institution decide what to improve next. Reports are scoped to the platform’s available data and the institution’s governance requirements. The handover covers user changes, software requests, maintenance notices and escalation, making the facility an ongoing service rather than a one-time equipment installation.
The proposal accounts for user groups, identity integration, applications, compute resources and migration from existing systems. Portal customisation, reporting, training and continuing administration are separate scope items. Share your current equipment and intended service rules to plan a platform that the local team can operate and extend.
Connected services & systems
Yes, where the hardware and software meet the required access and workload model. We assess support status, capacity and compatibility before deciding what to retain. Reusing equipment does not remove the need for storage protection, operating ownership or a tested deployment plan.
Project-based access and allocation can be part of the design. The implementation depends on the identity system, scheduler and storage platform selected. We test representative permitted and denied actions, rather than relying on labels in a user interface to establish separation.
Curobotic is based in Guwahati, Assam. We scope projects for organisations in Assam, Itanagar and other parts of Arunachal Pradesh, and Shillong. Remote preparation, site visits, freight and on-site installation are agreed in the quotation according to access, facilities and the work required.
Your next chapter starts here.
Share your workload, location and timeline. We will prepare a quotation for the agreed configuration and delivery scope.
admin@curobotic.com