Repository navigation
Expand file tree
/
Copy pathextension.html
More file actions
217 lines (199 loc) · 8.17 KB
/
Copy pathextension.html
File metadata and controls
217 lines (199 loc) · 8.17 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
---
layout: page
title: The Teampass browser extension
eyebrow: Productivity & security
lead: >-
Autofill and capture for Chrome, Firefox and Edge, talking only to your own
Teampass instance. It is the paid part of the project — and what keeps the
server free.
description: >-
The Teampass browser extension for Chrome, Firefox and Edge — autofill,
password capture and anti-phishing domain matching against your own
self-hosted instance. 30-day free trial.
cta:
- label: See pricing
url: /pricing.html
- label: Extension documentation
url: https://documentation.teampass.net/#/misc/extension
faq:
- question: What happens after the free trial?
answer: >-
The extension stops autofilling. Everything stays fully accessible through
the Teampass web interface — nothing is lost, nothing is locked.
- question: How are users counted?
answer: >-
By the number of unique accounts that used the browser extension during
the month. People who only use the web interface do not count against your
pack.
- question: Why doesn't it autofill on every site?
answer: >-
Some sites use non-standard forms, single-page frameworks or fields
injected after load, which cannot be detected reliably. On those, autofill
and capture can be triggered manually from the extension popup.
- question: Can we move up a pack during the year?
answer: >-
Yes. What you have already paid is deducted pro-rata.
- question: Does the extension see my browsing?
answer: >-
It matches the current domain against your stored items so it knows what
to offer. It does not collect browsing history, and nothing is sent to us —
see the <a href="/extension-privacy.html">privacy policy</a>.
- question: Why is it paid when the server is free?
answer: >-
Maintaining an extension across three browsers is continuous work — three
review processes and three sets of breaking changes every year. Charging
for it funds the open-source server instead of paywalling the server's own
features.
---
<section class="tp-section">
<div class="tp-container">
<header class="tp-section-header tp-section-header--center">
<span class="tp-section-header__eyebrow">The arrangement</span>
<h2>Teampass stays open-source. The extension goes further.</h2>
<p>
The server remains free, open-source and self-hosted — always. The
extension is a professional add-on for people who live in the browser all
day.
</p>
</header>
<div class="tp-grid tp-grid--4">
<article class="tp-card">
<span class="tp-icon-tile">{% include components/icon.html name="zap" %}</span>
<h3>Productivity</h3>
<p>Fill credentials in the tab you are already in. No window switching, no clipboard.</p>
</article>
<article class="tp-card">
<span class="tp-icon-tile">{% include components/icon.html name="shield" %}</span>
<h3>Security</h3>
<p>Domain matching means credentials do not offer themselves on a lookalike phishing page.</p>
</article>
<article class="tp-card">
<span class="tp-icon-tile">{% include components/icon.html name="download" %}</span>
<h3>Capture</h3>
<p>New sign-ups get saved into the right folder instead of a note somewhere.</p>
</article>
<article class="tp-card">
<span class="tp-icon-tile">{% include components/icon.html name="server" %}</span>
<h3>Sovereignty</h3>
<p>Your data never transits our servers. It moves between your browser and your instance.</p>
</article>
</div>
</div>
</section>
<section class="tp-section tp-section--alt" id="trial">
<div class="tp-container">
<div class="tp-split">
<div>
<span class="tp-section-header__eyebrow">Free trial</span>
<h2 style="font-size: 2.25rem; line-height: 1.2; margin-bottom: 16px;">Thirty days, whole team, no card</h2>
<p style="color: var(--tp-text-muted); margin-bottom: 24px;">
Every new instance gets a full month of the extension for every user.
Long enough to find out whether autofill actually changes your team's
habits — which is the only question that matters.
</p>
<a class="tp-btn" href="#activate">How to activate {% include components/icon.html name="arrow-right" %}</a>
</div>
<div>
<div class="tp-callout">
{% include components/icon.html name="info" %}
<p>
Available for <strong>Chrome, Firefox and Edge</strong>. Install it
from your browser's store, then point it at your own Teampass
instance.
</p>
</div>
</div>
</div>
</div>
</section>
<section class="tp-section" id="pricing">
<div class="tp-container">
<header class="tp-section-header">
<span class="tp-section-header__eyebrow">Pricing</span>
<h2>Buy capacity, manage your own access</h2>
<p>Simple, predictable, annual. No per-seat micro-management.</p>
</header>
<div class="tp-table-scroll">
<table class="tp-table">
<thead>
<tr>
<th scope="col">Pack</th>
<th scope="col">Capacity</th>
<th scope="col">Annual price</th>
<th scope="col">Suited to</th>
</tr>
</thead>
<tbody>
{%- for pack in site.data.pricing.packs %}
<tr>
<th scope="row">{{ pack.name }}</th>
<td>{{ pack.capacity }}</td>
<td><strong>{{ pack.price }}</strong></td>
<td>{{ pack.ideal }}</td>
</tr>
{%- endfor %}
</tbody>
</table>
</div>
<p class="tp-table-note">
Prices exclude taxes. Includes updates and email support.
Need something larger or a site licence?
<a href="{{ '/support.html' | relative_url }}">Ask for a quote</a>.
</p>
<div class="tp-pricing-promise">
<strong>{{ site.data.pricing.promise }}</strong>
</div>
</div>
</section>
<section class="tp-section tp-section--alt" id="activate">
<div class="tp-container">
<header class="tp-section-header">
<span class="tp-section-header__eyebrow">Activation</span>
<h2>Getting the trial running</h2>
</header>
<ol class="tp-steps">
<li class="tp-step">
<h3>Update your instance</h3>
<p>Install or upgrade to Teampass v3, then open <em>Settings > Extension</em> in the administration area.</p>
</li>
<li class="tp-step">
<h3>Install the extension</h3>
<p>From the Chrome, Firefox or Edge store.</p>
</li>
<li class="tp-step">
<h3>Send us two values</h3>
<p>
Email <a href="mailto:{{ site.email-commercial }}">{{ site.email-commercial }}</a> with the
<strong>FQDN</strong> of your instance and its <strong>instance token</strong>,
both shown in that settings screen.
</p>
</li>
</ol>
<div class="tp-callout" style="margin-top: 32px;">
{% include components/icon.html name="book" %}
<p>
Where to find those values, and every configuration option, is covered in
the <a href="{{ site.links.docs-extension }}" target="_blank" rel="noopener">extension documentation</a>.
</p>
</div>
</div>
</section>
<section class="tp-section">
<div class="tp-container tp-container--prose">
<header class="tp-section-header">
<span class="tp-section-header__eyebrow">Questions</span>
<h2>Straight answers</h2>
</header>
{% include components/faq.html items=page.faq %}
<p style="margin-top: 32px; font-size: 0.8125rem; color: var(--tp-text-muted);">
<a href="{{ '/extension-privacy.html' | relative_url }}">Privacy policy</a> —
the extension does not collect browsing data, and your credentials stay on
your own server.
</p>
</div>
</section>
{% include components/cta-band.html
title="Try it for a month."
body="Every new instance gets thirty days across the whole team, with no card and no commitment."
primary-label="See how to activate" primary-url="/extension.html#activate"
secondary-label="Read the pricing detail" secondary-url="/pricing.html" %}