Find hard-to-catch bugs before they impact your customers by testing with real browsers on real devices against your actual production backend.
And most importantly, no more fighting over staging or demo environments.
Use, share & comment on work in progress without breaking developer flow. Quickly get feedback from users, stakeholders and even customers.
Then release instantly at whatever pace suits you.
Have your developers focus on what truly matters to your organisation: building amazing products for your customers.
It takes only 15 minutes to get started with Linc. And it can be used in addition to your current pipeline, so you can phase out your current solution over time.
Every single commit has a unique URL for every backend. Now, the whole organisation can see & use any version against any backend, such as development, staging or even production.
From every preview link you can send a comment (with screenshot & metadata) straight into a Pull Request. No need for Github access.
We strongly believe that the information you need should be where you are working.
This is why we already integrate with Github PRs & Slack and are working on Trello, Jira & many other integrations to make sure everyone has all the information they need at their fingertips.
There are a lot of amazing testing tools out there. Browserstack to test across browsers, Calibre for performance testing, Percy for visual regression tests and many more. But integrating those into your pipeline can take hours, if not days, worth of work to do well.
That’s not the case with Linc.
And optionally, you can have every commit to master that passes all the tests be automatically deployed to your own production infrastructure.
Most of our customers bring a feature into Github on a branch, run all the tests, collaborate where needed and merge into master a short time later to be released to your customers in seconds.
Linc has streamlined our design and development process, and given us super-fast deployments.
Which has changed how our team, and even our entire business, operates.
We initially got Linc to streamline collaboration between our developers and designer.
But it also allowed us to easily involve clinical staff. Getting their feedback early is invaluable.
“We are a remote-first company and Linc has made it very easy for the development team to collaborate.
But it's also given me real visibility into the work that's getting done.”
A Front-end Delivery Platform (FDP) is a Continuous Delivery platform designed for the unique challenges of front-end delivery. Most importantly the gathering and organisation of feedback
And because there is a lot of variability in the pace of change between changes, it impossible to do that in a traditional linear pipeline. Every change needs to be deployed and available at any time.
By focusing on modern front-end applications, Linc can give you the best delivery platform money can buy. After setting up your build configuration, Linc will build, test & deploy every commit. And you can opt into any integration we offer. Right now that is Github, Slack and our own Linc Feedback and Auto Releaser. Browserstack & Trello are up next.
Netlify, Now and Heroku are all production hosting platforms with some preview functionality. But they are foremost hosting platforms, not delivery platforms. They do not easily allow your application to connect to multiple backends, nor do they have the integrated feedback features of Linc.
But as hosting platforms, they are very complementary to Linc and we will be supporting auto-deployments to Now and Heroku in the very near future.
Linc is build for modern front-end applications; Applications that run inside the browser that talk to backends over APIs. Linc supports frameworks like React, Angular, Vue, Ember and carefully handcrafted WebAssembly too.
One of the advantages of breaking up monoliths is the ability to vary the rate of change in parts of your application without affecting the rest of the system.
And that is the same with front-end applications. You can massively increase the rate of change (and experimentation) on your frontend, without any risk to your backend.