SSDO.

SSDO + SAS · by Solunex Technologies

Understand your database. Never hand over its data.

SSDO reads only the structure of a database (tables, columns, keys and links) and explains it, in plain language, with every statement marked as a fact or an inference. SAS is the separate gate for the rare time someone needs to see data: approved, limited and audited.

New to this? Start in 60 seconds.
  1. Open the Online shop sample: no sign-up, no database of yours needed.
  2. Read the map: each box is a table, each line a link. Solid lines are declared, dashed ones are inferred.
  3. Click a table to see its columns and the evidence behind each link.
SolaYour guide to the platform. Ask anything; no account needed.

Sola answers from Solunex's own pages. Nothing you type here is stored.

One platform, built around not seeing your data

SSDO

The map of how your database fits together. Ask it questions, watch it change while your team codes, and see what a change affects before anything runs.

SAS

The gate for when data must be seen: fixed kinds of question, owner approval, small groups hidden, sensitive columns masked, every step logged.

Academy

Lessons, quizzes, a practice lab and classes: learn how databases fit together without a database of your own.

Teams

Live rooms where the whole team sees each structure change as it happens, with mentors you invite for a time you choose.

Simulate and design

Draw a database that does not exist yet and get its SQL, then see how data would flow through it, using made-up files only.

Your tools

PostgreSQL, MySQL and MariaDB, SQL Server, Oracle and SQLite, GitHub pull requests, and AI coding tools that may see structure and never rows.

Development
Structure only — never your data. SSDO reads the database's layout (tables, columns, keys) from its metadata. It never reads, copies or stores a single row. Every conclusion below says whether it is a declared fact or an inference, and how sure SSDO is.

Your workspace

Point SSDO at a database. It reads structure only, no rows, and tells you what it knows as fact, what it infers with what confidence, and what it cannot know.

Map

The whole database, drawn from its structure.

App Simulation

Pick a table from a run in your vault and see what writing one row there would need: what must exist first, in what order, what you must provide, and what the database will not stop. Synthetic reasoning only. SSDO has not read, and cannot read, your data, and nothing here runs against your database.

Loading…

Change control

A structure change is requested by the person whose machine runs it, approved by a second person (an owner or admin who is not the author), and only then sent to the author's own terminal, where it still waits for yes. Every step is kept in an audit trail that cannot be edited. SSDO runs nothing.

Loading…

Governance

Each database your organisation registered: who answers for it, whether an admin approved it, whether SSDO is watching it, what its structure last did, and which column names look like personal or secret information. It describes; it changes nothing, and it reads no row.

Loading…

Environments

The same database lives in more than one place: your machine, staging, production. They are meant to have the same structure, and they drift. List them in the order changes travel, and SSDO says exactly where neighbours differ: tables, columns, kinds, keys, links and indexes. It compares the reads it already holds, connects to nothing and reads no data.

Loading…

Design a database

Describe a database that does not exist yet: its tables, columns, keys and links. There is no data here, and nowhere to put any. SSDO tells you what looks missing or fragile, writes the PostgreSQL that would create it (it runs nothing: you read it and run it), and lets you simulate how data would flow through it before you build anything.

Loading…

Discussion

Two databases understood together. Say what you intend, and SSDO shows the structure that matters for it. It describes; it never changes either database.

Coding workspace in the making

We are building this carefully and it is not available yet. Nothing on this page works today, and we have no date to give you. Here is what it is for, so you can tell us whether it is worth finishing.

Loading…

Referrals

Share your link. When someone you bring signs up, activates their account and pays, you earn 30% of what they pay for their first 12 months.

Loading…

Assistant

Ask a language model a question about a database's structure. It sees table and column names, types, keys and declared links, and never a row: SSDO does not have any. Optional, and off until an owner or admin turns it on. Its answers are suggestions, separate from SSDO's own findings.

Loading…

Local terminal

Ask your own database about its rows, safely, from your own computer. The terminal is SAS: it runs beside your database, so the data never comes to SSDO or to Solunex.

Loading…

SAS · the data layer

SAS answers approved questions about your organisation's data. It runs on your own computer, beside the database: the data never comes to SSDO or to Solunex.

Loading…
Loading…

Quizzes

Every question is built from a database's structure by a fixed rule, and graded by the same rule. A new attempt asks new questions; your best score counts.

Loading…

SAS Lab

Practise safe data access the way organisations do it: grants, masking, a fresh code to unmask, and an audit log nobody can quietly edit. On a fictional clinic, on your own computer: no real person is in it, and nothing comes to SSDO.

Practice databases

Starters written by hand by Solunex, never learned from anyone's database. Open one as your own draft database: read its map, ask about it, change it, and share it with your study group.

Loading…

Classes

Join your lecturer's class with a code, or run a class of your own. An assignment is a lesson's check or a level's quiz: it is graded by the same rules as everything else, and your lecturer sees only the work set for the class.

Loading…

Progress

What you have finished, level by level. Only which lessons you finished and when is kept, never anything you typed.

Loading…

Overview

Your watches, your rooms and what changed, in one place.

Loading…

Team

The people in this workspace, their roles, and its rooms. Owners and admins invite people and set the rules; each room's contents stay with the people who joined it.

Loading your team…

Plan & billing

Your workspace's plan, what it includes, and what you use. Limits only stop adding more: nothing you have is ever stopped or deleted. Security (email checks, two-step sign-in, sign-in alerts) is on every plan.

Loading…

Settings

Your own account, on every workspace you are in; and this workspace's name and rules, for its owner and admins.

Workspace

Keep working. ssdo watch runs next to your code, reads your database's structure every few seconds and sends it here only when it changed. Each change appears below the moment it happens, compared with the structure before it. Your database password never leaves your machine, and SSDO never connects to your database.

Study groups

Learn together. A group is a room for up to 6 people in your study space: chat and share screenshots, share a practice database, and set a group quiz to see how everyone is doing. Everything stays inside the group.

Loading your watches…

Vault

Every run your team has made, kept and never overwritten: structure, findings and your notes. Never a password, never a row of data. Pick runs to compare them, across time or across databases.

Loading your Vault…