A seat for every team.

GinzaOS brings your departments, people, customers and approvals into one workspace, with every change attributed.

The GinzaOS command center for a sample company, showing open work, at-risk accounts, a department pulse and recent activity.
Design preview running on sample data.

Companies rarely break inside a team. They break between teams.

Each department adopts its own tools, and soon the simplest questions take a meeting to answer. GinzaOS starts from the structure.

  • Who owns this account?Every case and customer has a visible owner and a queue.
  • Who can see it?Access comes from roles with explicit capabilities, per department.
  • Who changed it, and when?Changes are recorded with the person and time, as they happen.

Product

One structure. Each department in its seat.

Customer work with clear owners

Customer Success comes first: an account portfolio, a case queue with assignment and workload hints, SLA targets, saved views and reporting by department.

The Customer Success case queue for a sample company, with active, in-progress, high-priority and unassigned counts above a list of cases.

Access granted on purpose

Roles carry explicit capabilities, scoped to the whole workspace or one department. An assignment alone unlocks nothing.

The Roles and access page, listing role definitions with their capabilities.

Every change, attributed

Department moves, role changes, case updates and connection edits are written to the audit history in the same step.

The audit history, listing recent workspace events with who made each change and when.

Why a seat.

銀座, Ginza, was the silver guild of Edo, founded in 1612. A guild gave every trade a place, a standard and a record.

GinzaOS does the same for the teams inside a company. Our mark is a shelter over a single seat: the structure, and the one thing that needs you now.

Built to keep each company to itself.

  • Separate by design

    Each company's records are isolated in PostgreSQL with row-level security, and membership is checked on every request.

  • Your own sign-in

    Each workspace connects its own identity provider over OpenID Connect. Sessions rotate and expire.

  • Credentials stay private

    Connection secrets are encrypted, never sent to the browser and never written to the audit history.

  • Honest status

    Nothing is shown as connected until it has been verified. When something is missing, the screen says what.

Status

Where GinzaOS is today.

GinzaOS is in development. The screens on this page come from the working design preview, running on sample data.

Built in the preview

  • Organization and departments
  • People and reporting lines
  • Roles and access
  • Customer Success cases, SLA targets and reports
  • Approvals queue and audit history

In development

  • Sync with your CRM, help desk and HR system
  • Approval decisions
  • Sales, HR and Marketing workspaces
  • Payroll for Mexico and the United States
  • Invitations by email

Running a growing service company?

We are talking with operators who want one workspace for their teams. Tell us how your company works today.