Project templates land in your own repo

The biggest visible difference in this update is about new projects: if you create one from a template, the repository now lands in your own GitHub or GitLab organization — with the full history. On top of that, two subscription-related changes worth knowing about.

Creating a project from a template: the repo lands in your organization

When you create a project, Spedy can generate the code repository for you — New project → GitHub repository → Generate from template. This used to run through GitHub's "generate from template" feature, which tied the new repo to a single account. That's been replaced.

What happens now: Spedy creates a fresh, private repository in your own organization through your active Git integration, clones the template, and pushes it in there.

In practice:

• The repo is yours. It is created under your GitHub or GitLab namespace, not under someone else's account.
• GitHub or GitLab. The target follows your organization's active integration: if GitHub is connected, GitHub is used; if only GitLab is connected, the project is created in GitLab.
• Template and target are decoupled. A template hosted on GitHub can end up in a GitLab project — and the other way round.
• The full history comes along. Every branch and tag of the template is copied over, not just a starting state — including the prepared Docker stack for preview environments.
• The built-in Spedy templates (Shopware, Magento, Next.js) need no token. They are read without any credentials.

How to do it

1. Click New project in the sidebar
2. Enter a name and a prefix
3. Under GitHub repository, pick Generate from template
4. Choose the template you want from the list

The repository name is derived from the project name (lowercase, dashes). The generated repo is linked to the project right away and set as its preview repository.

You still register your own templates under Settings → Project templates; they are read with your own integration's token.

If something goes wrong: the empty target repository is created before the content is pushed into it. If the push fails, an empty repo is left behind — the error message names it. Delete it, or pick a different project name on the next attempt, otherwise the name collides. The project itself is kept: you can connect the repository later from the project settings.

Self-hosted GitLab: the instance has to be reachable at a public address. Internal addresses are rejected when creating and pushing.

When a subscription ends: read-only instead of a lockout

When a canceled subscription runs out, or a trial ends without a booking, the workspace now becomes read-only — instead of redirecting you to the billing page:

• Viewing and exporting keep working.
• Changes (creating tickets, commenting, moving cards) are no longer possible.
• A banner at the top of the app says so and links to Reactivate subscription.

The cancellation email matches that now: full access stays until the end of the paid period, after which the account continues with read-only access. There is no automatic switch to a free plan, and the period already paid for is not refunded pro rata.

Also newly visible: after a failed payment you now see a banner during the 14-day grace period asking you to update your payment method. That window used to pass without any notice at all.

Trial: plain wording at the start and before the first charge

The onboarding step for the Pro trial used to say "No credit card required" — which wasn't true, because starting it stores a payment method. The step now states what actually happens: a payment method is stored, a €0.01 verification is taken (refunded immediately), and after 30 days the plan continues as a paid one unless you cancel first.

The reminder email before the trial ends is clearer too. When a charge follows, it now names:

• the amount,
• the charge date,
• the number of seats,
• and the note that you can cancel any time until that date.

In short

• Project from a template: the new, private repository is created in your own GitHub or GitLab organization, with every branch and tag of the template. Template and target may live at different providers, and the built-in templates need no token.
• When a subscription ends: read-only access with export instead of a lockout, with a banner and a reactivate link — plus a visible notice during the 14-day grace period after a failed payment.
• Trial: onboarding and the reminder email name the payment method, amount, date and seats.