The platform is live. A private workspace for every engagement, and an agent that answers from your project or says it does not know.
Take a lookA private workspace
that knows, builds,
and launches your project.
Every engagement gets its own space. Upload the documents, connect the repositories, keep the decisions, and an agent answers only from that context, with citations, or says it does not know. Connect a repo and it opens pull requests you review, or describe a site and it builds and publishes it. We work in it together, and the context stays yours long after the work is done.
By invitation · a few founders at a time
This is my platform, and your project gets a private room inside it. The tools are the ones I built for my own work, opened up to the people I build with. We share one workspace, one source of truth, and one agent that will not invent an answer. The room stays open.
Context in. A grounded, cited answer out. Or an honest refusal.
You bring the context
Documents, PDFs, GitHub repositories, and the decisions that shaped the build.
It indexes and retrieves
Everything is split into passages, embedded, and searched with hybrid retrieval at question time.
You get a cited answer
Answered only from what was found, with a link to every source. Nothing found means it says so.
Or, on a connected repo
You describe the change
In plain language, in the same chat. A new endpoint, a refactor, a fix across a few files.
It edits in a sandbox
The agent reads the code, edits files in an isolated clone, and runs the build to check its own work.
You review a pull request
It opens a PR you read and merge. It never pushes to your main branch.
Describe it. Watch it build. Publish it live.
Start from a template or an existing repository. Describe the change in plain language and the agent edits real code in a sandbox, checks the build, and shows you the result in a live preview. When it looks right, publish it.
- Edited in an isolated sandbox, previewed live as it changes
- Published to a sites.alicantorun.com subdomain in one click
- Point your own domain at it, with the DNS records we verify
It refuses to make things up.
The agent searches your documents, code, and decisions, then answers only from what it finds. Every claim carries a citation you can click. Ask something outside your context and it will tell you it does not know, and list what it does have.
Cited by source kind
Three ways in. All of it answerable.
Uploads, code, and decisions land in one index, so a question reaches across all of them at once.
PDFs cite the page. Markdown cites the heading.
Cited by file and line, like index.js · L1-37. And editable by the agent, as a pull request you review.
Which database should we use?
PostgreSQL on managed RDS
Relational guarantees, mature ecosystem, cheaper to operate at our scale.
The decision log is folded into retrieval, so the agent can cite why, not just what.
It doesn't just read your repo. It changes it.
Connect a GitHub repository and the agent gets a second set of tools. Describe a change and it reads the code, edits files in an isolated sandbox, and runs the build before it proposes anything. You review the diff in the chat and open a pull request. It never pushes to your main branch.
- Edits a throwaway sandbox clone, never your machine.
- Runs a build check before it proposes the change.
- You open the pull request. The agent never pushes to main.
- A read-only clone token in the sandbox. The write is brokered by the portal.
Add rate limiting, request logging, and metrics
A sliding-window rate limiter, a request logger, a config module, and a GET /metrics endpoint, wired into the app. Verified with node --check.
Reviewed and merged on your terms
A board the client can actually read.
Tasks and milestones, on a board with drag between columns, a list, and a timeline. Every move is written to an activity trail, so the answer to what changed this week comes from the record, not from memory.
- Drag to move. Every move is logged.
- Group into milestones, filter to one.
- Board, list, and timeline of the same work.
Ask it to change the workspace.
The same agent can add and move tasks and record decisions. Turn auto-run on and additive changes take effect at once. Leave it off and each one waits for your approval. Deleting always asks first.
I found #5 Unassigned backlog item. Deleting is irreversible.
Search, ask, and add or move tasks and record decisions.
A token that can only read. Write tools are not even exposed.
Your workspace, on MCP.
Every workspace has its own MCP endpoint. Point your own Claude or Cursor at it with a bearer token and it gets the same grounded tools, scoped to your data alone. A wrong token, or the right token on the wrong workspace, is turned away.
11 tools · scoped by token · rotate or revoke anytime
One tenant. One dataset. A record of every look.
Isolation is the product. A workspace can only ever reach its own context, and everything sensitive is written to a trail the client can read.
Tenant isolation
Every query is scoped by workspace. One client's token cannot surface another client's documents, board, or code.
Roles that mean something
Owner, admin, and member. Members work in the workspace; only admins invite, rotate tokens, or delete.
Operator access is on the record
When the operator opens a workspace they are not a member of, a banner shows it and the trail records it.
Exported the workspace
torun.alican@gmail.com · northwind
Rotated the MCP token
torun.alican@gmail.com
Viewed a documentoperator
operator · as a non-member
Added a repository
torun.alican@gmail.com · acme-inc/platform
Events can never be edited, and go with the workspace when it is deleted.
Give your project a memory.
I work with a handful of founders at a time, and each engagement gets its own workspace. Tell me what you are building and I will set one up with you.