This is a roadmap, not a claim that the new workspace is live today.
Why we are changing direction Ident.ink has grown into several useful suites. The next step is to make the product feel like one deliberate place to run work, not a set of separate destinations. The workspace will be organised around an owned project, its people, its public site and the records that explain what happened.
One workspace, with the controls you choose The planned model is one business workspace with multi-tier subscriptions. Business, esports and developer workflows become configurable modules inside the same project. You can start with a small setup, add only what you need and switch between a ready-made starting point and a custom workflow without being forced to create records or follow a checklist.
Build your own operating view Visual blocks and node-style connections will let a team shape its own dashboard: recurring pay, approvals, client work, sponsor delivery, publishing, data and internal records can be arranged around the way that organisation actually works. Templates will be shareable starting points, clearly labelled as examples and never installed silently.
The studios stay part of the project Web Studio, video editing and photo editing remain connected to the same project context. A team can prepare its public identity, edit media locally where supported, manage access and publish to an Ident.ink subdomain or a domain it owns. Existing project data and permissions remain the boundary.
What stays true Existing suites and customer work are not being silently deleted or replaced. Payment authority remains explicit and Stripe-controlled. External APIs remain scoped, reviewed and unable to download or execute arbitrary code. The free tier will keep a useful public identity and project starting point; paid tiers will fund heavier hosting, storage, automation and connected operations.
Maintenance preparation During the week beginning 17 August 2026, we will prepare the platform for rolling maintenance. The target is to deploy in small, reversible steps behind health checks so public websites and customer work remain available. If a component needs intervention, only that component is isolated. We will publish measured status updates rather than promise an unverified uptime figure.
We will publish the implementation stages before changing customer workflows. Until then, this article is the source of truth for the direction and feedback is welcome through Support.
Nic Founder and Head Developer