The work starts at acceptance.
An accepted resident—artist or curator—receives a private profile with dates, onboarding, deliverables, meetings, and access information already in place.
Apply The private side of RUBY Projects
RUBY
NETWORK
A working space for residents and resident alumni: residency support, private documentation, opportunities, referrals, and the relationships that continue after the studio period ends.
Enter private network Refer an artist or curatorWhy RUBY built it
A residencyshould notdisappear into an inbox.
Residencies generate agreements, deadlines, studio visits, questions, photographs, introductions, and future opportunities—but those pieces usually scatter across email, texts, drives, and memory. RUBY NETWORK turns them into one continuing record that is useful to the resident and to RUBY before, during, and long after the residency.
The resident sees what RUBY sees.
Files, requests, deadlines, feedback, and decisions live in the same system, so nobody has to reconstruct the residency from an email chain.
Documentation becomes infrastructure.
Studio images and working notes can become an organized archive, exhibition material, press support, or the beginning of a future proposal—with the resident’s permissions attached.
The relationship keeps working.
When the residency ends, the profile becomes an alumni connection point for opportunities, referrals, introductions, and updates instead of going dormant.
One continuous record
Accepted →︎ Active →︎ Alumni.
RUBY NETWORK follows the actual life of the relationship, rather than treating residency as one isolated event.
- 01Acceptance creates the profile
Dates, residency type, onboarding, deliverables, and private access begin together.
- 02The resident gets oriented
Arrival details, goals, technical needs, meetings, and required materials are visible from one place.
- 03Work moves through review
Uploads reach the correct resident record; RUBY can respond, approve, request changes, or assign a follow-up.
- 04The residency becomes an archive
Useful documentation retains its context, status, permissions, and relationship to the work.
- 05Alumni stay connected
RUBY can share relevant opportunities and make thoughtful introductions without relying on a public feed.
A deliberately small network
Not another
social platform.
There is no algorithm, follower count, or pressure to perform publicly. Access is tied to a real RUBY relationship. The value comes from shared context: RUBY knows the work, the resident knows the program, and every introduction can begin somewhere more useful than a cold message.
FOR RESIDENTS
Less chasing. More clarity.
- One place for dates, deliverables, files, meetings, and feedback
- Private documentation with clear permissions
- Requests and needs that reach the person who can act on them
- A continuing relationship after the studio period ends
FOR RUBY
Better support. Better memory.
- A live view of what each resident needs and owes
- Files and decisions attached to the correct person and project
- Earlier visibility into problems, opportunities, and follow-ups
- A useful alumni network built from actual shared work
The map is public. The relationships are protected.
From somewhere.
Connected here.
The public map shows the geographic reach of RUBY. RUBY NETWORK holds the more useful layer: what members can offer, what they need, and how RUBY can connect them—visible only to the people inside it.
Explore the public Resident Alumni mapPrivate by design · Useful by practice
Already part of RUBY?
Enter your resident, alumni, or admin workspace to continue where the relationship left off.
Enter private network