Public status, in real time.
The status page asks for no login and sits behind no authorizer, and no component has a switch: its state derives from the worst open incident affecting it. Nobody has to remember to raise the flag — and nobody can forget to lower it.
What comes with it
Everything S7 Support does
Your ticket
Open it, follow it, close it — with the whole thread in view.
Bug, question or request
Three ticket types, a required title and the product involved when it matters. No active Space needed to ask for help.
Immutable thread, official reply marked
Nothing is edited or deleted once sent, and a reply from whoever runs the platform arrives flagged as official.
Attachments that are pointers
Up to five files on the ticket and on every reply. The bytes stay in your storage; support only carries the ids.
You close what is yours
A ticket travels from open to closed; whoever opened it can close it any time, and two simultaneous edits warn instead of overwriting each other.
What comes next
What the platform builds next starts here — and it is counted in people.
A request board with votes
Feature requests are visible to anyone who signed in. Voting is one click, and the count is of people: pressing again does not move the number.
Ask for what does not exist yet
A provider with no adapter, a product in the oven: the demand counter records how many people asked — never who asked.
The "I want this" button in any product
Any screen on the platform opens this form already filled in through a link — no integration and no coupling between products.
The board shows the title, and that is all
The server sends a reduced projection: title, product, state and count. Descriptions and authors never cross from one person to another — and bugs are not voted on, bugs get triaged.
Status and incidents
The part anyone can reach, including people with no account.
S7 Status, no login
An open page shows every component's state, the incidents under way and the recent history — no login and no personal data.
A timeline that only grows
Every incident update lands at the end of the public timeline. Nothing is rewritten, so the whole story can be read back later.
State is not an opinion
Each component inherits the worst open incident affecting it: minor, major or outage. With no open incident, operational.
An incident is born explaining itself
Whoever runs the platform declares it with a public title, an impact and the affected components — and the first message is already the first entry of the timeline. There is no silent incident.
From ticket to reply, nothing lost
A ticket is yours, not the Space’s: you open it wherever you are and it stays yours. When the problem is everybody’s, it becomes an incident — and then the answer turns public.
You open it
Type, title, detail and attachments. From any product, through a link.
The platform triages
Whoever runs it sees the whole queue and moves the ticket along.
The reply lands in the thread
Flagged as official, with an attachment when it needs to show.
If it is general, it becomes an incident
The ticket gets the link and you follow it on the status page.
The view of whoever keeps the platform up
An admin is whoever the deploy names: a list of users read as the function starts, with no flag stored in a database and no claim in the token. An empty list takes the function down instead of serving the admin area as if it were an ordinary user.
Every ticket in one queue, with a state filter and a move to any state.
Overview: Spaces, known users, who signed in within the window and the most voted requests.
A paginated user directory, with each person’s Spaces, role and the products they used.
A Space directory with owner, active members and products in use.
Email and name do not live here: the directory keeps ids and resolves identity at identity with the admin’s own session. If that lookup fails, the table shows the ids and carries on.
What holds it up
The guarantees that come along
Space verified, never trusted
The Space in the token is only stamped onto the ticket after it is checked against the real membership — and having no Space at all stops nobody from asking for help.
A ticket is between two parties
Only the person who opened it and whoever runs the platform can read a ticket. To everyone else it does not exist — the answer is "not found", the one way an id cannot betray what exists.
What reaches the bus is ids
Titles, descriptions and comments never become events. The rest of the platform learns that a ticket changed state, not what it says.
Three languages, one product
Portuguese, English and Spanish across the whole interface — including the status page, which serves all three at the same address.