The NSF-DOE Vera C. Rubin Observatory’s Legacy Survey of Space and Time (LSST) began its formal 10-year survey on June 30, 2026, from the Simonyi Survey Telescope on Cerro Pachón in Chile. It will image the entire visible southern sky every few nights for a decade, generating one of the largest research-data streams any single facility has ever produced. For research administrators and data-services staff supporting astronomers — or anyone assessing what “open” actually means for a megaproject of this scale — the practical question isn’t whether Rubin/LSST data exists, it’s who is allowed to touch it, when, and through what system. This page focuses specifically on those access mechanics, centered on the second Data Preview (DP2), the current on-ramp for the wider research community.
This page is scoped to data access, not authorship. CASRAI already covers how Rubin/LSST papers assign author credit in Astronomy Survey Authorship: How SDSS, DESI, and Rubin/LSST Compile Author Lists. That is a separate question from who can pull data out of the archive in the first place — Rubin’s data-rights system (below) gates raw data access, while each thematic Science Collaboration sets its own, independent authorship rules on top of that. Read this page for the access mechanics; read the linked guide for how credit gets assigned once you have the data.
What DP2 actually is (and isn’t)
Data Preview 2 is not the start of the operational survey’s own data releases — it is a preview built from commissioning-period observations. Per Rubin Observatory’s own DP2 documentation, the release comprises image and catalog products from Rubin Science Pipelines v30 processing of observations taken with the LSST Camera between April 2025 and January 2026, ahead of the survey’s June 30, 2026 start. An early release emphasizing catalog data and deep coadd images is scheduled for July 27, 2026, with the fuller processed dataset (comprehensive imaging and photometric products) expected between October and December 2026.
DP2 is the latest in a sequence of preview releases Rubin has used to let the community build and test analysis tools before the survey’s own annual Data Releases begin: DP0 (simulated data, no real observations), DP1 (Rubin’s first preview built from real commissioning-camera data), and now DP2 (the first preview built from the actual LSST Camera). Each successive preview has moved closer to the real instrument and real survey-scale data volumes.
Who can access LSST data: the data-rights model
Rubin/LSST does not use open, unrestricted public access for its raw and proprietary data products. Instead it uses a defined “data rights” eligibility gate, set out in Rubin Observatory’s Data Policy. Data rights are held by:
- All scientists and students at accredited US educational or research institutions conducting non-profit research (with a path for unaffiliated researchers, such as serious amateur astronomers or independent students, to request access if public resources are insufficient for their needs);
- Professionals and students in Chile, as defined in coordination with the Sociedad Chilena de Astronomía (SOCHIAS);
- Named individuals on Rubin’s International In-Kind Data Rights Holders list, negotiated through in-kind contributions to the LSST community; and
- Junior researchers moving between qualifying institutions, covered under a grace-period provision so a mid-career move doesn’t instantly cut off data access.
Only Rubin data-rights holders can hold an account on the Rubin Science Platform (RSP) and access DP2 or other proprietary Rubin data products. There is no separate “buy” or “request individual access” route into the RSP itself for non-rights-holders — the eligibility categories above are the access mechanism.
Rubin describes its underlying principle as “no reserved science”: no team, however large, gets exclusive early scientific claim over the data beyond the standard proprietary period described below. Researchers without data rights can still participate in Rubin/LSST science — they can co-author papers built on Rubin data and work with derived data products that don’t reconstruct the underlying proprietary data — but they cannot independently query or download proprietary products themselves. That distinction (participation in the science vs. direct data access) is exactly the boundary between this page and CASRAI’s separate astronomy survey authorship guide.
How access actually works: the Rubin Science Platform
For eligible data-rights holders, the Rubin Science Platform (RSP) is the primary access point, offering three interfaces:
- Portal — a browser-based graphical interface for data discovery and visualization, no coding required for basic queries.
- Notebook — a hosted JupyterLab environment for scripted analysis directly against Rubin’s data holdings, without downloading full datasets locally first.
- API — remote, IVOA (International Virtual Observatory Alliance) standards-based programmatic access, letting existing virtual-observatory tooling query Rubin data the same way it queries other observatories’ archives.
Through the RSP, rights-holders can reach the Prompt Products Database (transient-object light curves and moving-object detections) and the two most recent annual Data Releases once the operational survey’s release cadence begins. Beyond the RSP itself, several other routes carry specific Rubin data products to a wider audience regardless of data-rights status: public alert brokers redistribute the nightly alert stream, the Minor Planet Center receives solar-system object detections, and independent, community-run Data Access Centers (IDACs) can mirror select products under their own terms.
What’s actually public, and what’s embargoed
Not all Rubin data products carry the same restriction. Per Rubin’s Data Policy:
- Alert stream — public immediately. Individual alert packets, generated within roughly 60 seconds of each image, can be redistributed worldwide to anyone, rights-holder or not, typically via public alert brokers.
- Prompt Products Database — public, accessible without data-rights status.
- Prompt-processed images and annual Data Releases — a two-year proprietary (embargo) period applies from release. During that window only data-rights holders can access and analyze these products; after two years they become publicly available.
Data Previews sit inside that same rights-gated model: DP2 access, like DP1 before it, is restricted to data-rights holders through the RSP for the duration of its preview status. This is the same embargo logic CASRAI documents generally under Embargo — a defined, time-limited restriction period after which access rules change — applied here at observatory scale rather than to a single dataset or article.
What research administrators and data-services staff should track
- Verify data-rights status before promising access. Institutional affiliation with a qualifying US or Chilean institution, or a named position on the international in-kind list, is a prerequisite for an RSP account — confirm status before a researcher builds a project plan around DP2 access.
- Treat the two-year embargo as a real compliance date in any Data Management Plan (DMP) or funder data-sharing plan that references Rubin/LSST products, the same way you would track any other embargo clause or repository release date.
- Distinguish data access from authorship rights. A researcher (or a collaborator without formal data rights) may be entitled to co-author a paper using Rubin data without ever holding an RSP account themselves — see the separate authorship guide for how that gets negotiated inside individual Science Collaborations.
- DP2 is not yet survey-proper data. Anything published from DP2 is built on commissioning-period observations (April 2025-January 2026), not the operational survey that began June 30, 2026 — useful context when interpreting early DP2-based results or advising on citation/versioning language.
- Downstream products still need standard data-stewardship practice. Institutions publishing derived Rubin datasets to a data repository should still apply ordinary FAIR data practice and check funder data-sharing policy requirements independently of Rubin’s own access tiering.
Frequently asked questions
Can any researcher get a Rubin Science Platform account?
No. An RSP account requires Rubin data-rights status — qualifying US or Chilean institutional affiliation, or being a named international in-kind data-rights holder (with a narrow request-based path for unaffiliated researchers when public tools aren’t sufficient). There is no general-public or pay-for-access route into the RSP.
Is any Rubin/LSST data public with no restrictions at all?
Yes. The nightly alert stream and the Prompt Products Database are public immediately, regardless of data-rights status. Prompt-processed images and full annual Data Releases carry a two-year proprietary period before becoming public.
Is Data Preview 2 the same as the survey’s first official data release?
No. DP2 is a preview built from pre-survey commissioning observations (April 2025-January 2026) with the LSST Camera, released ahead of and separately from the operational survey’s own future annual Data Releases. The operational 10-year survey itself began June 30, 2026.
Does lacking Rubin data rights block someone from co-authoring an LSST paper?
No, not on its own. Rubin’s “no reserved science” policy explicitly allows researchers without data rights to collaborate and co-author papers using Rubin data; it’s the raw/proprietary data access itself, not co-authorship eligibility, that is gated by data-rights status. Authorship criteria beyond that are set independently by each Science Collaboration — see CASRAI’s Rubin/LSST authorship guide.
Primary sources: Rubin Observatory, Data Access and Analysis; Rubin Observatory, Data Policy; Data Preview 2 documentation (dp2.lsst.io); Rubin Observatory, “Action! NSF-DOE Vera C. Rubin Observatory Begins Capturing the Greatest Cosmic Movie Ever Made”.
