GitLab compared with Magpie

GitLab vs Magpie: an in-depth comparison

GitLab and Magpie both host Git repositories, track issues and publish a website from a repository. GitLab is built around shipping the code. Magpie is built around the business the code is written for.

  1. GitLab is a platform for planning, writing, reviewing, testing, securing and shipping code. It runs on GitLab.com or on your own servers. It is built for software teams and the companies that run them. They review each change in a merge request and run a pipeline on every push.
  2. Magpie is one subscription for a small business's software. Git Repositories and Issues are two of its areas. Beside them it includes websites, Time Tracking, Invoicing, a Client Portal, Team chat and the rest. It is built for a small team whose code is one part of running the business.
Create account
Callahan Studio’s private albers-coffee-site repository, with its folders and files, the last commit and its HTTPS clone address.

How is Magpie different?

1. The code comes with the rest of the business

One Magpie subscription includes the areas a small business would otherwise buy one at a time:

  • Git Repositories for private and public repositories, cloned and pushed over HTTPS or SSH
  • Issues, with a board, projects, milestones, cycles, triage and automation rules
  • Websites, with an editor website or a files website built from a repository on each push
  • Time Tracking, Invoicing and a Client Portal for the client the work is for
  • Team chat, Documents, Mail, Meetings, Store and the other areas, in the same team

Everything is in one account with one bill. GitLab covers code, review, CI/CD, security and planning. Invoices, bookings and email are left to other software.

2. One price for the whole team, and guests take no place

A Magpie team pays one price for its plan, not a price per person. The Team plan has places for 25 members. A guest is given only the areas they need, such as Git Repositories or Issues. A guest takes no place on the plan: a paid plan allows 100 guests.

3. Bug reports, time and client updates are in one tracker

A public issue form takes a bug report from anyone, with no account. Each report waits in Triage. Start timer on an issue records the time spent, and that time can go on an invoice. A Client Portal shows a client each shared project's status and target date. It does not show the issues or comments.

Comparing Magpie and GitLab

GitLab does more with the code itself; Magpie does more around it. Every line in the tables below was checked against GitLab's own pages, linked from each row, and against Magpie's code and Help.

Platform

WhatGitLabMagpie
Git hostingPrivate and public repositories, cloned and pushed with Git Yes Yes
Code on the websiteFiles, history, branches and each commit's changed lines Yes Default branch, no line changes
Editing files in the browserChange files and commit them without Git on a computer Web IDE No
Merge requests and code reviewPropose a change, review it and merge it Yes No
CI/CD pipelinesBuild, test and deploy jobs on every push Yes No
Packages and container imagesLibraries and images for others to install Yes No
Coding in the browserA ready-made development setup online Workspaces, Premium No
Security scanningCode flaws, committed keys and vulnerable libraries Yes No
AI for codeWrite, explain and review code GitLab Duo Reads repositories
Issue trackingIssues with labels, milestones and sub-issues Yes Yes
Boards and sprintsPlan the work and follow its progress Yes Yes
Epics and a roadmapLarger pieces of work on a timeline Premium Projects, listed by date
Requests by emailCustomers email in a problem and get answers Service Desk Public issue form
Website from a repositoryA site published on each push Pages Yes
Website editorBuild pages on screen without code No Yes
Time tracking and invoicingRecord time on an issue and bill for it Time tracking, no invoices Yes
Incidents and on-callPage whoever is on call and time the fix Premium No
Your own serverInstall and run it yourself Self-Managed No
Phone appFollow the work on a phone No In the browser
Single sign-onSign in through a company identity provider Premium No

Good to know: Where Magpie says No or Partly, the line under the row says what Magpie does instead. Each gap has an item on Magpie's roadmap, and the line changes on the day it ships.

Source code management

Both host private and public repositories that Git clones and pushes. GitLab shows every branch, each commit's changed lines and who last changed each line. It edits files in the Web IDE and keeps large files with Git LFS. They do it better than we do today.

WhatGitLabMagpie
Create a repository with a README to start from Source Yes Yes
Keep a repository private, or make it public Source Yes Yes
Clone, pull and push with Git from my computer Source Yes Yes
Read a repository's files and commit history on the website Source Yes Yes
Work on a branch, and choose any branch to read on the website Source Magpie: Git pushes any branch to a Magpie repository, but the website shows only the default branch and cannot create or delete one. The Magpie app lets you choose a branch to read, but it is not yet in the App Store or Google Play. Yes Partly
Change files on the website and commit them, without Git on my computer Source Magpie: Files are read-only on the website; only the description and visibility change there. Changes arrive by pushing with Git. Yes No
See what a commit or a branch changed, line by line Source Magpie: A commit is listed with its message, author, date and short ID; nothing shows the lines it changed. People read the changes with Git on their computer. Yes No
See who last changed each line of a file Source Magpie: A file shows its contents and the last commit that touched the file as a whole, not each line's. Yes No
Search the code across my repositories Source GitLab: Basic search finds code inside one project only. Searching code across groups or the whole of GitLab needs advanced search or exact code search, which an administrator turns on.Magpie: Git Repositories searches repository names and descriptions; Search and the assistant do not search inside the code, though the assistant can read a file you name. Partly No
Rename a repository or move it to another group, keeping old links working Source Magpie: A repository's name and default branch cannot be changed after it is created, and it cannot move to another team. A new repository with the right name, pushed again, is the way round it. Yes No
Keep large files such as videos and images in a repository Source Magpie: Git Large File Storage is not supported; a repository holds only what ordinary Git pushes. Yes No
Publish a release with notes and files to download Source Magpie: Tags can be pushed, but a repository has no releases page, release notes or attached downloads. Store sells files when a download should be paid for. Yes No
Keep a project's documentation pages beside its code Source Magpie: Markdown files in a repository, the README included, show as formatted documents on its page and its public page. There is no wiki to edit on the website; longer guides go in Documents. Yes Partly
Bring a repository over from GitHub or another host Source Magpie: An empty repository shows the commands to push one you already have, so its whole history arrives with Git from your computer. Magpie cannot fetch a repository from GitHub or another address by itself. Issues imports a CSV file or a GitHub Issues export. Yes Partly
Keep a repository in step with a copy on another host, automatically Source Magpie: A repository changes only when someone pushes to it. Magpie neither copies it to another host nor fetches from one. Yes No
Give a server or a script access to one repository only Source Magpie: A token can read, write or both, but it belongs to a person and works for every repository that person can reach, and so does an SSH key. Nothing can be limited to one repository. Yes Partly

Good to know: A new Magpie repository can start with a README, a .gitignore and a license. A public repository can be read and cloned by anyone without signing in.

Merge requests and code review

GitLab reviews each change in a merge request, with protected branches on every plan. Premium adds required approvals, code owners and push rules. Magpie has none of these yet; changes are merged with Git on a computer and pushed.

WhatGitLabMagpie
Propose a change on a branch, discuss it line by line and merge it Source Magpie: There are no merge requests. Members merge with Git on their computer and push; Issues can link to a GitHub pull request but does not review one. Yes No
Require approval from the right reviewers before a change is merged Source Magpie: There is no review step, so nothing can be required before a change reaches the default branch. Yes No
Stop people force-pushing over or deleting the main branch Source Magpie: Anyone with write access can push, force-push or delete any branch. The push check reads branch rules, but nothing in Magpie lets a member set one. Yes No
Refuse pushes that break our rules, such as a missing issue number or a file that is too big Source Magpie: A push is checked only for access. Magpie has no rules about commit messages, branch names or file sizes. Yes No
Copy someone else's repository to change it, and offer the change back Source Magpie: A public repository can be cloned and pushed to a new repository, but the copy is not connected to the original and cannot offer a change back. Yes No

Good to know: In Magpie, access to a team's repositories follows the team's Member access setting. A team that gives members view access lets them read and clone, not push.

CI/CD, packages and Pages

GitLab runs pipelines from a .gitlab-ci.yml file and records each deployment. It also hosts packages and container images. Both publish a website from a repository on each push. Magpie runs nothing else on a push.

WhatGitLabMagpie
Run build and test jobs on every push Source Magpie: There is no job runner. A push can rebuild a website made from the repository, and nothing else runs. Yes No
Deploy to staging and production, see which version is live in each, and roll back Source Magpie: Only a website made from a repository is deployed: each build is a version, and Restore brings an earlier one back. There are no environments, and nothing is deployed to your own servers. Yes Partly
Publish packages and container images beside the code Source Magpie: Magpie holds Git repositories only; packages and images are published to another registry. Yes No
Tell another app when code is pushed or something changes Source Magpie: A push only rebuilds a website made from the repository. Webhooks exist for Issues, not for repositories. Yes No
Publish a website from a repository on every push Source Yes Yes
Publish a site built with Hugo, Jekyll or another generator Source Magpie: Magpie builds its own Markdown and Twig format. A Jekyll or Hugo site has to be built on your computer and its output pushed, which is published as it is. Yes Partly
Show a site only to the people on the project Source Magpie: A published website is open to anyone; turning off Published takes it offline for everyone. Yes No
Write and run code in a ready-made setup in the browser Source Magpie: Code is written and run on your own computer and pushed to Magpie. Yes No

Good to know: A Magpie files website made from a repository builds on each push to its branch. Build now makes it at once, and a failed build keeps the live site and its log.

Planning and project management

Both track issues on boards, under milestones and in sprints. GitLab's epics, iterations, several assignees, weights and roadmap need Premium. Magpie's projects, sub-issues, cycles and timers are on every plan.

WhatGitLabMagpie
Write down a bug or a piece of work as an issue Source Yes Yes
Move issues across a board from to do to done Source Yes Yes
Sort issues with labels, including sets where only one can apply Source Magpie: Labels are shared by the team, any number go on an issue, and the list filters by them. A Select custom field holds one value from a set, such as a type, and priority is built in. The list can show a custom field as a column and sort by a Number or Date field, but cannot filter or group by one, and the board cannot either. Yes Partly
Group issues under a milestone with dates, and see how far along it is Source Yes Yes
Group issues under a larger piece of work, broken down in levels Source Yes Yes
Plan work in sprints that are made for us and carry unfinished work over Source Magpie: Cycles are one week, two weeks or a custom length, and show completed, in progress and remaining issues. Each cycle is made by hand, and unfinished issues stay in it until someone selects them and moves them on. Yes Partly
Assign an issue to several people Source Magpie: An issue has one assignee, any member who can use Issues. A User custom field can name someone else. Yes Partly
Give each issue an estimate of its size, and see the total Source Magpie: An issue has no estimate or size, so cycles and projects count issues, not effort. A Number custom field can hold a size, but nothing adds it up. Yes No
Record the time spent on an issue Source Yes Yes
See charts of how a milestone or sprint is going Source Magpie: Projects, milestones and cycles show counts of completed, in progress and remaining issues; nothing draws them as a chart or over time. Yes Partly
See epics and milestones on a timeline Source Magpie: Roadmap lists projects that have a start or target date, earliest first, with their status and progress. It is a list, not bars on a timeline, and milestones and issues are not on it. Yes Partly
Start a new issue from a ready-made outline that asks for the details we need Source Magpie: A public issue form gives outsiders instructions and asks for a title, a description and an optional email address. A member's new issue has no starter outline. Yes Partly
Let customers email in a problem and answer them, without an account Source Magpie: A public issue form takes a report from anyone without an account and puts it in Triage. Issues has no email address and cannot reply to the reporter, and Helpdesk answers customer email but cannot make an issue from it. Yes Partly
Close an issue when the commit or merge request that fixes it lands Source Magpie: An issue in a project linked to a GitHub repository lists GitHub pull requests and commits added by hand. Commits pushed to Magpie's own repositories are not linked to issues and close nothing. Yes Partly

Good to know: A Magpie cycle is one week, two weeks or a custom length. A public issue form takes reports from people without an account. Each report waits in Triage.

Security and compliance

GitLab scans the code and its commits for flaws and keys on every plan. Ultimate adds dependency scanning and refuses a push that holds a key. Magpie does not scan a repository.

WhatGitLabMagpie
Find security flaws in my code automatically Source Magpie: Magpie does not analyse the code in a repository. Yes No
Be warned, or stopped, when a password or key is committed Source Magpie: Pushes are not checked for keys or passwords. Yes No
Be warned when a library my code uses has a known security hole Source Magpie: Magpie does not read a repository's dependencies or images, or warn about them. Yes No
See who in the team did what, and when Source Magpie: A team's admins see an audit log of who changed its members, the areas each can use, invitations, guests, API keys pinned to it, its Stripe account, owner and archiving, with the IP address, kept 12 months and exported as CSV. Pushes, repository changes and sign-ins are not in it; each issue and Kanban board keeps its own activity. Yes Partly

Good to know: An HTTPS token in Magpie is shown once and can read, write or both. It works for every repository your account can open.

GitLab Duo

GitLab Duo suggests code in your editor, answers questions in a chat and reviews merge requests. It runs on GitLab Credits. Magpie's assistant reads repositories and does not write code.

WhatGitLabMagpie
Have AI write code, answer questions about it and review a change Source Magpie: The assistant reads a repository's branches, recent commits, file tree, README and a file you name, and answers questions about them. It does not write code, commit or review changes. Yes Partly

Good to know: The assistant reads a repository's branches, recent commits, file tree, README and a file you name. It answers questions about them.

Plans, people and hosting

GitLab charges per user and gives each person one of its default roles. It also installs on your own servers. Magpie charges one price for the team and runs only as Magpie's own service.

WhatGitLabMagpie
Give each person the access they need: read, write or manage Source Magpie: Team admins read, push and manage, and every member has the same access to all the team's repositories: push with the team's edit access, read and clone with view access. On the website an admin can keep a member out of Git Repositories or give a guest the whole area, but cannot give members different levels. The Magpie app shares one repository with one person outside the team, read-only or read and write, but it is not yet in the App Store or Google Play. Yes Partly
Make our own roles with exactly the permissions we choose Source Magpie: A team admin chooses which areas each member can use, and members either edit or only view, set for the whole team; guests use only what they are given. There are no roles made of single permissions. Yes Partly
Sign in through our company identity provider Source Magpie: People sign in with a password and two-factor code, a passkey, a sign-in link, or an Apple, Google, LinkedIn or GitHub account. Yes No
Run it on our own server Source Magpie: Magpie runs only as Magpie's own hosted service. Yes No
Pay one price for the whole team, not per person Source GitLab: Premium is priced per user a month, billed yearly, and Ultimate is priced per user on request. Free on GitLab.com allows five users in a private group. No Yes
Let people outside the team see and comment without paying for them Source GitLab: A Guest can view and comment on issues in a private project but cannot read its code. Guests take a paid seat on Premium and are free only on Ultimate. Partly Yes
Follow and change the work from my phone Source GitLab: GitLab has no mobile app of its own; a request for one is open in its own issue tracker, so people use the website or apps made by others. No Yes

Good to know: A Magpie guest takes no place on the plan. Free allows 10 guests, and a paid plan 100. A team's admins see an audit log of changes to its members, guests and API keys.

Incidents and analytics

On Premium, GitLab pages whoever is on call and times incidents. It also measures how quickly the team ships. Magpie has none of these. It turns the time spent on issues into invoices.

WhatGitLabMagpie
Page whoever is on call when something breaks, and pass it on if they do not answer Source Magpie: Magpie has no alerts, on-call rotas or paging. An issue's assignee is notified when it is assigned to them. Yes No
Count down to the deadline for fixing an incident Source Magpie: A due date is set by hand. An automation rule can raise the priority, but no rule sets a deadline. Yes No
See how quickly the team ships changes Source Magpie: Magpie has no figures about how code reaches production; Issues counts completed issues in projects, milestones and cycles. Yes No
Bill a client for the time spent on issues Source GitLab: Time spent is recorded on issues and merge requests and listed in reports; nothing turns it into an invoice. No Yes

Good to know: Time from an issue's timer goes into Time Tracking. Once it is billable, Add unbilled time puts it on the client's invoice.

Price comparison

How GitLab charges

GitLab has a Free plan and charges Premium per user, per month, billed yearly. Ultimate is priced on request. Free on GitLab.com allows 5 users in a private group and 400 compute minutes a month. Premium adds required approvals, epics, push rules, single sign-on and more minutes. Ultimate adds security scanning, free guests and the most minutes. GitLab Self-Managed is free to install. Prices are on GitLab's pricing page.

How Magpie charges

Magpie charges by plan, Free or a paid plan, for everything in the account. Git Repositories and Issues are on every plan, the Free plan included. A team's plan is one price for the whole team, not a price per person. Prices are on Magpie's pricing page.

On top of the planGitLabMagpie
How a team paysPer user, per monthOne price for the team
People on the free plan5 users in a private group3 people in a free team; 25 on the Team plan
Guests who read and commentA paid seat, except on UltimateNo place taken: 10 on Free, 100 on a paid plan
Compute minutes400 a month on Free, 10,000 on Premium, 50,000 on UltimateNot offered
Security scanningCode scanning on every plan; dependency scanning and push protection on UltimateNot offered
AI for codeGitLab Credits, bought on Free and included for now on Premium and UltimateThe assistant reads repositories, included
Running it yourselfSelf-Managed, free or on a paid planNot offered
Website from a repositoryPages, on every plan1 website on Free, 20 on a paid plan
Time tracking, invoicing and a client portalTime tracking on every plan; no invoicingIncluded

When to choose Magpie or GitLab

  • Want repositories and issues beside time tracking, invoices and your website, at one price for the team? Go with Magpie.
  • Want merge requests, pipelines and security scanning, on GitLab.com or on your own server? GitLab is the right choice.

Recommendations by kind of business

For a software team that reviews every change
GitLab. Merge requests, protected branches and pipelines guard the main branch on every plan. Premium adds required approvals and code owners. Magpie has none of these yet.
For a company that must keep its code on its own servers
GitLab. GitLab Self-Managed installs on your own servers, free or on a paid plan. Magpie runs only as Magpie's own service.
For an agency or freelancer building for clients
Magpie. An issue's timer records the time, and that time can go on an invoice. The Client Portal shows the client their project's status. GitLab records time but sends no invoices.
For a small team that pays per person today
Magpie. A Magpie team pays one price for up to 25 members, and guests take no place. Repositories, Issues and a website from a repository are on every plan.
For a product team that answers customers by email
GitLab. Service Desk gives a project an email address, and the team answers each ticket by email. Magpie's public issue form takes reports without an account, but cannot reply to the reporter.
For a team planning work in sprints
Either. Both have boards, milestones and sprints. GitLab's epics, iterations and roadmap need Premium; Magpie's projects, cycles and sub-issues are on every plan. Choose GitLab to keep the plan beside merge requests. Choose Magpie to keep it beside the rest of the business.

Frequently asked questions

What is the difference between GitLab and Magpie?

GitLab is a platform for planning, writing, reviewing, testing, securing and shipping code. It runs on GitLab.com or on your own servers. Magpie is one subscription for a small business's software. Its Git Repositories and Issues are two areas beside Websites, Time Tracking, Invoicing and the rest. GitLab does more with the code itself; Magpie does more around it.

Does Magpie replace GitLab?

Yes, for a small team that pushes to private repositories and tracks work as issues. Magpie hosts the repositories, plans the work and publishes a website on each push.

Consider keeping GitLab if you review changes in merge requests or run a pipeline on every push. Keep it if you need security scanning or a package registry. Keep it too if your code must stay on your own servers. GitLab does each of these better than Magpie does today.

How much does GitLab cost?

GitLab has a Free plan, Premium priced per user, and Ultimate priced on request. Free on GitLab.com allows 5 users in a private group and 400 compute minutes a month. Premium includes 10,000 minutes, and Ultimate 50,000. GitLab Self-Managed is free to install. The prices are on GitLab's pricing page.

How much does Magpie cost?

Magpie has a Free plan and paid plans, each covering every area. Git Repositories and Issues are on every plan. A free team has places for 3 people. The Team plan has places for 25, at one price for the team. The prices are on Magpie's pricing page.

Does Magpie have merge requests?

No. Members merge with Git on their computer and push the result. Nothing in Magpie reviews a change or requires an approval before a merge. Merge requests are on Magpie's roadmap. GitLab's merge requests hold the change, its discussion, its pipeline and its approvals.

Does Magpie run CI/CD pipelines?

No. A push to a repository can rebuild a website made from it, and nothing else runs. Build jobs are on Magpie's roadmap. GitLab runs jobs from a .gitlab-ci.yml file, with 400 compute minutes a month on Free.

Can I see what a commit changed in Magpie?

No. Commits lists each commit's message, author, date and short ID, without the lines it changed. People read the changes with Git on their computer. GitLab shows every changed line of a commit or a merge request.

Does Magpie show branches other than the main one?

No, not on the website. Git pushes any branch to a Magpie repository, but its page shows only the default branch. The Magpie app can choose a branch to read. It is not yet in the App Store or Google Play. GitLab lets you choose any branch or tag.

Can I edit a file on Magpie's website?

No. Files are read-only on the website, and changes arrive by pushing with Git. GitLab's Web Editor changes one file, and its Web IDE changes several and commits them.

Does Magpie check my code for security problems?

No. Magpie does not scan the code, check pushes for keys or read a repository's dependencies. GitLab scans the code and its commits on every plan. Dependency scanning and push protection need Ultimate.

Does Magpie support Git LFS?

No. A Magpie repository holds only what ordinary Git pushes. GitLab's Git Large File Storage is on by default, on every plan.

Does Magpie have a wiki?

No. Markdown files in a repository, the README included, show as formatted documents on its page. Longer guides can go in Documents. GitLab gives every project a wiki, edited on the website or pushed with Git.

Can I run Magpie on my own server?

No. Magpie runs only as Magpie's own hosted service. GitLab Self-Managed installs on your own servers, free or on a paid plan. GitLab Dedicated is a hosted copy kept apart from other customers.

Does Magpie have epics and a roadmap?

Partly. A project groups issues with a lead, a status, dates and a count of completed issues. Any issue can have sub-issues, several levels deep. Roadmap lists dated projects, earliest first, not as bars on a timeline. GitLab's epics and roadmap need Premium.

Does GitLab have time tracking or invoicing?

GitLab has time tracking and no invoicing. Time spent is added to an issue by hand or with a /spend command, on every plan. Nothing turns it into an invoice. In Magpie, Start timer on an issue records time in Time Tracking. That time can go on an invoice.

Can customers report a bug without an account?

Yes, in both. GitLab's Service Desk gives a project an email address. Each email becomes a ticket, and the team replies by email. GitLab says Service Desk is no longer under active development. Magpie's public issue form takes a title, a description and an optional email address. Each report waits in Triage. Magpie cannot reply to the reporter from Issues.

Does Magpie have an AI that writes code?

No. The assistant reads a repository's branches, recent commits, file tree, README and a file you name. It answers questions about them, and does not write code, commit or review changes. GitLab Duo suggests code, answers questions, turns an issue into a merge request and reviews merge requests.

Does GitLab have a phone app?

No. GitLab has no official app; a request for one is open in GitLab's own issue tracker. People use the website or apps made by others. Magpie's Git Repositories and Issues work in a phone's browser, the issue board included.

Does Magpie have a phone app?

Git Repositories and Issues work in a phone's browser, the issue board included. The Magpie app has them too. It is not yet in the App Store or Google Play.

Can I publish a website from a repository on Magpie?

Yes. A files website takes its files from a repository in the team. Each push makes the site again. Markdown pages with Twig layouts are built; anything else is published as it is. A Jekyll or Hugo site is built on your computer first. GitLab Pages runs any generator in a pipeline job.

Can I use GitLab and Magpie together?

Yes. A team can keep merge requests and pipelines on GitLab and plan, bill and publish in Magpie. Git can push the same repository to both, so a Magpie files website builds from each push. Magpie's Issues links to GitHub, not to GitLab.

How do I move a repository from GitLab to Magpie?

Create a repository in Git Repositories without starter files and copy its clone address. In your clone, add that address as a remote. Push every branch and tag to it. Over HTTPS, Git asks for a password: paste a Magpie token. Over SSH, add your key in Magpie first. Merge requests, the wiki, pipelines and releases stay on GitLab.

Can I bring my GitLab issues into Magpie?

Partly. GitLab exports a project's issues as a CSV file on every plan. Import issues in Magpie reads a CSV file. You choose which columns fill the title, description, labels, assignee and due date. Labels and assignees must already exist in the team. GitLab writes its times in a different form, so created and closed times are left out. One import creates up to 200 issues.

What is included in Magpie's Free plan?

Git Repositories, Issues, 1 website, Time Tracking, Invoicing, Store, Meetings, Forms and a team of 3. A paid plan raises the limits and adds email at your domain.

If a line on this page is wrong, tell us and we will correct it.

GitLab changes, and so does Magpie. If a line is out of date about either product, email support@magpie.diy with the page that shows it. We check the line against that page, change it, and give it the new date. That goes for GitLab's own team as much as for anyone who uses it.

Put your code beside the rest of the business.

Create a Magpie account, then make your first Git repository.

Create account