Project management and delivery analysis for vendors building and maintaining Goa Government projects.
Your account was created for you, and the password you were emailed works only this once. Pick your own to continue — nobody else can see it, including the administrator who set the account up.
Tell us about your company. An administrator reviews every registration before the account can sign in.
Delivery and site status for everything your connected services can reach, plus the projects you have added by hand.
One project per row; the first line names the columns, in any order: name (required), owner, live_url, description, nodal_name, nodal_email, nodal_phone, platforms (ids separated by ;), tags (separated by ;), status (active · on_hold · completed · decommissioned). Rows with a problem are shown and skipped; the rest are recorded in Periscope only — nothing is created on any host. Download a template.
| Line | Project | Owner | Live URL | Nodal officer | Platforms / tags | Result |
|---|
Periscope reads your repositories, pipelines and deployments from GitHub. Connect a token to see them here.
| refresh | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Repository list capped — raise PERISCOPE_REPO_PAGES to load more.
status-check, health, uptime, probe or ping), and with neither it shows
Unknown rather than a guess. Hover a badge to see which source it came from.
CI/CD status and site status stay deliberately separate: a passing pipeline is not a live site.
Your account and the services it is connected to.
Connect wherever your projects live. Periscope only ever reads from these services — it can never change, trigger or delete anything. Each token is verified with the service and then encrypted before it is stored.
Which service each vendor has connected and the account it reads as. A vendor connects their own token; Periscope reads their repositories with it, and your dashboard uses the same token for their projects. A token is never shown to anyone.
| Vendor | GitHub | GitLab | Active projects | Status |
|---|---|---|---|---|
| Loading… | ||||
A project on one of these can still be tracked — add it by hand from the dashboard and Periscope will follow its site, certificate and security audit.
Each project's engagement: type, period, value and the signed order. Reminders go out 60, 30, 7 and 0 days before an order ends, and an invoice prompt 30 days before.
| Project | Type | Period | Days left | State | Reference | Value | Document | Recorded by | Actions |
|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||
The accounts on the platform, what each owns and what needs their attention, and the scheduled reminders that go to them.
Once a day the server sends the expiry reminders itself — audit 60/30/7/0 days, SSL 30/7/0 — to the vendor who owns each active project, with the nodal officer in copy, each step once. Every week it sends administrators a digest of what needs attention.
Loading…
Registrations arrive as pending and cannot sign in until approved. You can also add a vendor directly — an account you create is active straight away. Archive suspends a vendor and archives every project they own in one step (nothing is deleted; move a project to another vendor first if it should live on).
| Company | Contact | Phone | Role | Status | Projects | Attention | Last sign-in | Actions |
|---|